I'm using a BizTalk orchestration published as a web service to call JDE
EntOne. Currently, I'm catching errors that are returned from the LOB
adapter
as a soap exception. I'm not defining a fault message on the
solicit-response
****t or using a general exception as suggested by the LOB do***entation. I
really want to get to the specific error message so I can potentially pass
it
back to the client app or log it etc.
The error handling works fine, and JDE exceptions are getting caught but I
still always end-up with a suspended SOAP fault message (0xc0c0167a
Transmission Failure). If I am catching and handling the error returned by
JDE in the orchestration, why I am still getting a suspended message of
the
same error that must be manually or otherwise terminated?
To be clear, the request is successfully sent to JDE but in the case of a
bad param value, the JDE business function throws an exception that is
returned to BizTalk. In addition, I get the suspended message if I handle
it
as a soap exception or as a general exception.
Recommendations on how to better handle JDE EntOne errors or how to
prevent
the suspended message appreciated.
--
RT
