Hi, I noticed a recent jira comment that indicates the context component is deprecated[1] I couldn't find anything in the code or documentation that indicates deprecation. Is there now a better alternative for the kinds of use cases the context component supported?
[1] https://issues.apache.org/jira/browse/CAMEL-9200 Thanks, -Aaron On Thu, Oct 8, 2015 at 4:07 AM, Antonin Stefanutti <anto...@stefanutti.fr> wrote: > Hi Aaron, > > Great. I’ll test your patch and comment on the JIRA ticket then. > > Antonin > > > On 08 Oct 2015, at 07:13, Aaron Birkland <ap...@cornell.edu> wrote: > > > > I've opened up an issue and attached a pach to it: > > https://issues.apache.org/jira/browse/CAMEL-9200 > > > > I'm not entirely familiar with the Camel code, but this patch addresses > > everything that seemed obviously problematic to me. > > > > Thanks, > > Aaron > > > > On Wed, Oct 7, 2015 at 12:48 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. > >> > >
