I'm using Processor interface, to handle the incoming SOAP request from the
Exchange and apply some business logic on it, Based on the business logic I
wanted to invoke different camel routes (defined in camel context xml),
hence ProducerTemplate to invoke different camel routes.
Regards,
Nithesh
Normally you don't want to shut it down until the application is shutting
down. And then it should happen of its own accord.
Another question is why are you using the Processor interface? Unless
there's a compelling reason just use a regular old Java bean. In a lot of
these cases you don't even n
Thanks for your valuable response,
Now I'm using ProducerTemplate to invoke a camel route by injecting the
template as below:
public class Test implements Processor {
@EndpointInject(uri="direct:invokeWS")
ProducerTemplate producer;
@Override
public void process(Exchange exchange
After going through with a fine tooth comb, I think the issue might be the
instance of connection factory. The only difference between your test case
and what I am doing is that I am getting the connection factory by doing a
jndi lookup on a resource adapter that is configured in my jboss j2ee
cont
I am pretty sure, since I traced the message at all the 3 hops and ensured it
has the same correlation id
1. tracer on the producer side
2. On the AMQ console
3. tracer on the consumer side
It might be a misleading exception, also, the same thing works if I use an
instantiated connection factory v
