Willem - I should upgrade to 2.5 first and see if I can reproduce but it's
not as straight forward as hoped I am afraid.
Btw - I am defining the routes programmatically at startup time such as -
...
RouteBuilder.... {
public void configure() {
from(source).process(myProcessor).to(destination);
}
It all works fine on pub/sub scenarios. But on synchronous request/response
the processor is called only on the inbound route but not outbound returning
the response. I suppose with JMS messaging, the response is sent on a temp
queue, which actually doesn't have a route with this processor defined.
How do I get the processor to process bidirectionally?
Cheers.
--
View this message in context:
http://camel.465427.n5.nabble.com/JAXB-causing-Unit-Test-Failure-without-any-actual-marshalling-active-tp3278807p3284642.html
Sent from the Camel - Users mailing list archive at Nabble.com.
