|
| return a nice Fault message, instead of the dull |
 |
Tue, 15 Apr 2008 09:44:15 EDT |
I know I'm x-posting here, but I wasn't able to move my question from the
"middleware something" forum...
I'm working with the Websphere Integration Developer(WID) and I've got some
WSDL's which does not include the Fault element.(unmodeled faults)
This means there will be no visual Fault connections in the WID Mediation flow
editor, and I haven't been able to extract the context.failInfo element and
direct that into the headers.SOAPFaultInfo element.
All I get from the ESB is a dull unexpected exception.
soapenv:Server.generalException
com.ibm.websphere.sca.ServiceRuntimeException: CWSXM0202E: An unexpected
exception occurred when processing mediation flow for component LoggerMediation
in module LoggerMediation: caused by:
com.ibm.wsspi.sibx.mediation.flow.MediationRuntimeException: CWSXM1025E: An
unexpected exception occurred during flow invocation: CWSXM0111E: Service
runtime exception invoking an import from mediation component LoggerMediation in
module LoggerMediation: CWSXM0205E: An unexpected business logic exception
occurred.
But when debug'in, I see in the context.failInfo:
soapenv:Server.generalException WSWS3713E: Connection to the remote host
webserviceHost failed.Received the following error: Connection refused: no
further information
|
| Post Reply
|
|
|
|
|
|
|
|
|
|