ndpoint 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.
> >>
>
>
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.
>>
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
> 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.
>
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
Hi All,
I had some time to dig into this issue, and it appears more severe than I
had initially thought. Right now, there is *no* isolation between endpoint
names between camel contexts. In fact, using the context component in its
current state results brings *local* endpoint names from referenc
Hello,
I'm having a strange problem with the camel context component and think it
may be a bug. I've created a unit test that currently fails:
https://gist.github.com/birkland/1b12261521dd5d5c79ef
Basically, I'm trying create a 'parent' camel context that routes a message
through two 'black bo
