Hi,
I just checked the code and found the RoutingSlip is using the camel
context from the exchange to resolve the endpoint.
That can explain what you find :)
On Fri Sep 23 19:15:18 2011, Andrei Shakirin wrote:
Hi Ioannis,
Hmm ... I do not think so.
If camel-core.jar loaded in the same classloader
(http://camel.apache.org/vm.html) it works. And it is exactly the case if both
bundles uses the same version of camel-core bundle.
Basically communication works, I have my RoutingSlip called with correct
exchange.
The confusing point is why endpoint returned by RoutingSlip is trying to
resolve using old Camel Context (from the first bundle).
If the same endpoint is defined statically in camel route spring configuration
- it resolved using actual Camel Context (from the second bundle).
For me is unexpected behaviour.
Regards,
Andrei.
-----Original Message-----
From: Ioannis Canellos [mailto:[email protected]]
Sent: 23 September 2011 12:28
To: [email protected]
Subject: Re: Camel uses old context to resolve endpoint by routing
I think that the vm can only be used to bridge contexts that are in the same
bundle.
--
*Ioannis Canellos*
*
FuseSource<http://fusesource.com>
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf<http://karaf.apache.org/> Committer& PMC Apache
ServiceMix<http://servicemix.apache.org/> Committer Apache
Gora<http://incubator.apache.org/gora/> Committer
*
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
