You can get faultString etc. like in the catch block,

exception.getFaultString()

Upul

On Feb 1, 2008 3:38 AM, <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I am having some problems getting the FaultString out of the SOAP message
> returned to me from a service.
>
> I have generated my stubs using WSDL2Java from version 1.3 of Axis2.
>
> The following is the SOAP message returned :
>
>
> <soapenv:Envelope
>     xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>     xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
>     xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> <soapenv:Header/>
> <soapenv:Body>
>    <soapenv:Fault>
>       <faultcode  xmlns:p773="
> http://exception.enterpriseservice.mincom.com
> ">p773:EnterpriseServiceConnectionException</faultcode>
>      <faultstring><![CDATA[
> com.mincom.enterpriseservice.exception.EnterpriseServiceConnectionException:
> CTG9631E: Error occurred during interaction with CICS. Error
> Code=ECI_ERR_NO_CICS, error code: -3]]></faultstring>
>      <detail encodingStyle="">
>           <p773:EnterpriseServiceConnectionException xmlns:p773="
> http://exception.enterpriseservice.mincom.com";>
>                 <p773:ellipseConnectionManagerLogonResultDTO
> xsi:nil="true"/>
>          </p773:EnterpriseServiceConnectionException>
>      </detail>
>     </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
> However, the stub throws an EnterpriseServiceConnectionException which
> contains a null ellipseConnectionManagerLogonResultDTO (which I guess makes
> sense from the result).
>
> I want to know if the faultstring is made available to the client stubs(as
> this is what holds the meaningful message in this case), and if so, how?
>
> Thanks
>
> Julie
>
> --
>
> This transmission is for the intended addressee only and is confidential
> information. If you have received this transmission in error, please notify
> the sender and delete the transmission. The contents of this e-mail are the
> opinion of the writer only and are not endorsed by the Mincom Group of
> companies unless expressly stated otherwise.
>
> --
>
>
>
>
>
>
>
>
>
>
>

Reply via email to