Hi Antonin, Thank you very much. Part of the patch involves having the Context component mint 'exported' Endpoints that have noops for several operations that looked dangerous to me (like setCamelContext).
I'll create an issue this evening, and place the fixes in a cloned repository in github. Thanks again, -Aaron On Oct 7, 2015 12:49 PM, "astefanutti" <anto...@stefanutti.fr> wrote: > Hi Aaron, > > I've been able to reproduce your issue and your analysis is correct. > > The Endpoint returned by the context component has its reference to its > original black-box Camel context overwritten when the 'parent' context adds > it to its list of service. There is a clear design issue not only from the > address space but for the lifecycle of the endpoint as well. > > You can create a JIRA ticket and I'll review / test your patch. > > Antonin > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Context-Component-issue-tp5770975p5772383.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
