Hi one thing I once did and it worked out quite good was to register the SEDA component from one route as a Service now I used that one not to communicate between bundles but to communicate with the bundle that provided it as a service. It worked out quite good and I didn't need any other extra infrastructure.
Regards, Achim 2011/5/5 boday <[email protected]>: > I researched this a while back and it I think the Camel approach to > communicating between bundles was to use JMS, NMR or WebServices (instead of > sharing the camel context). The pure OSGi way is to use the service > registry or manifest import/export package statements. > > Anyways, I wrote this > http://benoday.blogspot.com/2010/08/osgi-bundle-communication-options.html > blog post when evaluating options are a client. If you land on an > alternate solution, let me know... > > > > ----- > Ben O'Day > IT Consultant -http://benoday.blogspot.com > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Problem-designing-a-camel-route-for-an-OSGi-system-tp4363426p4371567.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- -- *Achim Nierbeck* Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead
