Hi Chirstian,
You can export the interceptor as OSGi service, and import the service
as a bean with the help of Spring DM.
Then you can share the interceptor across the Camel context and the OSGi
bundle.
Willem
----------------------------------
Apache Camel, Apache CXF committer
Open Source Integration http://www.fusesource.com
Blog http://willemjiang.blogspot.com
Tiwtter http://twitter.com/willemjiang
Christian Mueller wrote:
Hello list!
We are using Camel 2.2.0-fuse-02-00 inside FUSE ESB 4.2.0-fuse-02-00. We
only use Camel for our integration requirements (no JBI). Our first
integration solution contains approximate 15+ OSGI bundles. Each OSGI bundle
consists of one Camel context. This means we will deploy 15+ different Camel
context. We will also use (our custom) Trace component to audit our message
flows.
Do we have to define the Trace component in each bundle? As described
[here|http://camel.apache.org/advanced-configuration-of-camelcontext-using-spring.html]
(Using container wide interceptors), it is possible to "share" interceptors
between different Camel context. Is this only possible it they are defined
in the same Spring configuration? Or is this also possible in an OSGI
environment like ServiceMix where another Camel context reside usually in
another OSGI bundle?
Thanks in advanced for your time and help,
Christian
