Thank you very much
--
View this message in context:
http://camel.465427.n5.nabble.com/Add-a-Processor-to-a-route-at-runtime-tp4257724p4267611.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Look at the unit of work on the exchange as it contains message
history details. In rhe the current route id as well.
On Monday, March 28, 2011, JacobS wrote:
> Thanks the java predicate works but I still have problem identifying the
> route that is being checked for interception.
> I tried usi
Thanks the java predicate works but I still have problem identifying the
route that is being checked for interception.
I tried using the 'exchange.getFromEndpoint().getEndpointUri()' but this
only returns the endpoint which originated this message exchange .
Is there a way to get the RouteId in
Just use java code to build a custom Predicate that computes this, and
use it with the onWhen on the interceptor.
On Wed, Mar 23, 2011 at 9:56 AM, JacobS wrote:
> Looks like interceptFrom could be the right way to go.
> How can I add a predicate to the interceptFrom that will intercept according
Looks like interceptFrom could be the right way to go.
How can I add a predicate to the interceptFrom that will intercept according
to a header and the routeID ?
Something like this:
${in.getExchange.getFromRouteId} ==
${in.header.interceptFromRouteID} />
On 3/23/11 3:07 PM, JacobS wrote:
I am adding plugins functionality to my app and I want the plugins to be able
to add processors to the existing routes. I don't know in which route or
where in the route the plugin would want to add some logic thats why I
wanted to add the processors at runtime.
I am adding plugins functionality to my app and I want the plugins to be able
to add processors to the existing routes. I don't know in which route or
where in the route the plugin would want to add some logic thats why I
wanted to add the processors at runtime.
Can 'Camel Intercept' help me with
Can I know why you want to add Processor into the route?
I don't think current Camel provides that kind of API you want.
You may consider to use this handy Intercept[1] of Camel instead of add the
processor to the route.
[1]http://camel.apache.org/intercept.html
Willem
JacobS wrote:
>
> Hi
>