Hi Sergey, I tried doing this, encapsulating and exposing what functionality I wanted, so that my client bundles wouldn't need to be camel-aware. Yes, it can be done, as long as you're willing to create front-ends for whatever you want to do.
I ended up thinking it was more trouble than it was worth, especially when I needed to deal with the actual exchange. At that point it just seemed easier to let the bundles be camel-aware. Don On Wed, Jun 22, 2011 at 11:11 AM, Zhemzhitsky Sergey <sergey_zhemzhit...@troika.ru> wrote: > Hi there, > > I'm using the latest version of camel and I'm wondering whether it is > possible to export a camel endpoint as OSGi service, so any non-camel-aware > code can transparently use camel functionality in OSGi environment. And in > that case from the OSGi service consumer's point of view, camel context is a > simple OSGi service. > > Best Regards, > Sergey Zhemzhitsky > > > _______________________________________________________ > > The information contained in this message may be privileged and conf idential > and protected from disclosure. If you are not the original intended > recipient, you are hereby notified that any review, retransmission, > dissemination, or other use of, or taking of any action in reliance upon, > this information is prohibited. If you have received this communication in > error, please notify the sender immediately by replying to this message and > delete it from your computer. Thank you for your cooperation. Troika Dialog, > Russia. > If you need assistance please contact our Contact Center (+7495) 258 0500 or > go to www.troika.ru/eng/Contacts/system.wbp > >
