Juan,
If you register an endpoint for your service in the NMR, you can access
it from you camel orchestration bundle. The camel-nmr shows you how
different Camel routes can communicate over the NMR, but you can connect
anything there. A service that has an endpoint registered on the NMR,
is not necessarily available for remote calls.
Whether or not you expose a service to remote calls, is entirely up to
you. Many applications only expose a few (web)services to the outside
world, while working with a lot of different services for the
implementation.
For the log: endpoint, that actually refers to a Camel component
(http://activemq.apache.org/camel/log.html) which uses the
commons-logging API. The only thing OSGi does here is provide the
classes from the logging bundle to the camel-core bundle. If this is
what you want to, just take a look at any components in Camel for an
example.
Regards,
Gert
Juan F. Valdés wrote:
I'm reviewing EIP osgi documentation and camel-osgi example and I have a
doubt.
I want to develop one bundle that orchestrates request calling services from
other bundles, and I would like to intercept those calls with camel, it is
posible?
I think probably I will have to register an endpoint for my service in NMR,
but, If I do so, have i to expose the service to remote calls? (with cxf or
jms bc), I don't want that.
I saw there is a destination endpoint called log:ExampleRouter in camel-osgi
example that references Commons logging Bundle. It seems that it is a kind
of logical link between osgi and NMR endpoint and could be what I need for
my application, ¿how can i do that for my bundles?
Thanks In Advance,
Juan.
