Assuming the scenario I have 2 jbi endpoints: - 'jbi:myInOutEndpoint' with MEP=InOut; - 'jbi:myInOnlyEndpoint' with MEP=InOnly;
and the following route in camel: <route> <from uri="jbi:myInOutEndpoint"/> <setExchangePattern pattern="InOut"/> (...) <to uri="jbi:myInOnlyEndpoint" /> (...) </route> 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? att. *Henrique Viecili *
