[
https://issues.apache.org/jira/browse/CAMEL-21628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21628:
--------------------------------
Fix Version/s: 4.10.0
> camel-core: Make AggregateProcessor set the CamelContext on its
> AggregationRepository
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-21628
> URL: https://issues.apache.org/jira/browse/CAMEL-21628
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: James Netherton
> Assignee: James Netherton
> Priority: Minor
> Fix For: 4.10.0
>
>
> Minor thing I stumbled across while working on something in the Infinispan
> component.
> There's some code where the CamelContext is supposed to be propagated from
> InfinispanRemoteAggregationRepository to InfinispanRemoteManager:
> https://github.com/apache/camel/blob/401a6367aec8c311c170d127e75ec5f07f1a9de0/components/camel-infinispan/camel-infinispan/src/main/java/org/apache/camel/component/infinispan/remote/InfinispanRemoteAggregationRepository.java#L94
> getCamelContext() actually returns null because it's never been set. By
> chance, there's no code (yet) within InfinispanRemoteManager that actually
> refers to the context. But we should avoid passing in a null value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
