-
1. Re: JMS Service Binding & transferException Option
igarashitm Jun 2, 2014 10:09 AM (in response to michaelclay)transferException is not supported in SwitchYard today - feel free to file a JIRA as a feature request. Camel sends the Exception back as a reply when transferException=true and just rethrows the Exception when transferException=false.
-
2. Re: JMS Service Binding & transferException Option
michaelclay Jun 2, 2014 10:22 AM (in response to igarashitm)is there some other way to handle and propagate Exceptions (Messages) back to a jms consumer otherwise i consider this as a blocker for the usage of jms service bindings since as outlined above the client consumer will always timeout because there is no way to return a message - do i miss something here?
-
3. Re: JMS Service Binding & transferException Option
igarashitm Jun 2, 2014 10:37 AM (in response to michaelclay)You want to put the Exception into replyTo Queue anyway? then you would need to try-catch in the camel route and forward it to the JMS endpoint explicitly for example.
-
4. Re: JMS Service Binding & transferException Option
michaelclay Jun 2, 2014 11:29 AM (in response to igarashitm)no i simply need a hook into sy to catch and handle exceptions - i have a try-catch in my route but it is never executed !
if you need a repro for this take the soap-proxy example change the service binding from soap to jms and return a SOAPMessage with a SOAPFault from the proxied webservice + wrap the 'ReverseService' reference call into a try catch.
with the current implementation you will never get a response message