Hello Camel! I was wondering how routes could be extensible.
I thougth I could use the following idea to do it but I appears to be otherwise: The route I created is pretty simple: It picks up message from A, transform it then send it to B. I would like to make it extensible so that another route could be hooked into it. My idea was to divide the route into 2 routes: 1) A -> transform -> properties:hook-in 2) properties:hook-out -> B By default hook-in and hook-out would use the same direct:hook endpoint or anything like that. If another route transporting messages from C to D needs to be added, the properties can be changed to - hook-in=C - hook-out=D That way the route would be complete. However, since I deploy the route as separate osgi bundles (one with A->B, another with C->D), I get the following error CamelExchangeException: No consumers available on endpoint: Endpoint[direct://hook-in] Another complication is that I would like the route to stay transactional and only have A and B persisted on my JMS broker. Is that possible ? -- View this message in context: http://camel.465427.n5.nabble.com/Hookpoint-Extensible-routes-tp3201249p3201249.html Sent from the Camel - Users mailing list archive at Nabble.com.
