1 Reply Latest reply on Feb 25, 2009 5:09 AM by Kevin Conner

    faultTo in asynchronous continuation

    Erik W. Rasmussen Newbie


      I have a problem implementing a synchronous web service using JBoss ESB beneath. I am using asynchronous continuation in the same manner as described in this post: http://www.jboss.org/community/docs/DOC-9105

      The problem is error handling. The behaviour regarding the faultTo address is to remove it in a request-response mep when returning (this was apparently caused from this jira: https://jira.jboss.org/jira/browse/JBESB-1158).

      Referring to the sample code of the above posting: I call the Service1 with a faultTo address. However when the Service1Continuation is called the faultTo address has been removed because the previous service called was a RequestReponse mep. This means that any errors occurring in the Service1Continuation will not be sent to the original faultTo address but to the dlq. And hence the web service will never receive a reply.

      The only thing I can think of here is never to use RequestResponse mep. Any other suggestions?

        • 1. Re: faultTo in asynchronous continuation
          Kevin Conner Master

          You are correct that the RequestResponse mep will strip the FaultTo from the response although this is similar to the original ReplyTo behaviour.

          If you wish to propagate the fault to then you should modify the InitContinuationAction class to store the FaultTo EPR in addition to the ReplyTo.

          This value can then be used within your continuation pipeline to send a fault in a similar manner to the response (ContinuationResponseAction) with the exception that the action would be triggered by the processException method and should be registered as the first in the continuation pipeline.