I have experienced the exchange hanging, waiting for a response to continue
after <to uri="jbi:myInOnlyEndpoint" />. And of course this is my mistake,
cause I should have properly set up the route with pattern="InOnly".
But it would be much easier to identify this mistake if at some point
(deploy time or runtime) camel would warn me about calling an InOnly
endpoint with an InOut exchange.
Is there a way to enable such warnings? Do they already exist? Where should
I start looking in camel or servicemix code to create a patch?
Re: Calling an InOnly endpoint with an InOut exchange...
Is it mandatory that you uses the jbi endpoint component or can you interconnect your camel routes directly using direct component, ... ? As jbi will become deprecated in next releases of Apache ServiceMx, I recommend that you investigate alternatives like NMR nmr which allows to move camel objects in async mode or direct-vm for sync exchanges direct-vm.