camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier.Roger" <olivier.ro...@bsb.com>
Subject Re: [Hookpoint] Extensible routes ?
Date Mon, 21 Feb 2011 12:49:28 GMT

Hello JacobS,

The solution we put in place is based on the previous comments.

The idea was to split the route into a least two OSGI bundles.

The first bundle gather all endpoint definition to external systems, like
ftp, web service, jms, ... anything really. All the incomming messages
received on those endpoint are transported to the NMR component.
The contrary is also true, all outgoing messages are sent to those endpoint
with a route that listen to an NMR endpoint.

This first bundle contains all the configuration to a specific environment,
we have one for each application server we use for instance.

On top of that one or more bundles can be plugged in and reuse those
endpoint with pure camel. To be able to change the hookpoint, we use the
config service which allows to change the route endpoint at runtime.

I hope this helps,

Olivier
-- 
View this message in context: http://camel.465427.n5.nabble.com/Hookpoint-Extensible-routes-tp3201249p3394096.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message