3 Replies Latest reply on Aug 25, 2005 7:27 PM by Thomas Diesler

    SOAPFault instead of custom Exception

    Andre Simon Newbie

      Hi

      On JAX-RPC Clientside I became a SOAPFaultException instead of a custom Exception. I compare my WSDL File and JAX-RPC-MAPPING File with the testsuite examples, everything seems right.

      The SOAP Message I´ve got :

      
      <?xml version="1.0" encoding="UTF-8"?>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <soapenv:Body>
       <soapenv:Fault>
       <faultcode>soapenv:Client</faultcode>
       <faultstring>message<faultstring>
       <detail>
       <MyException xsi:type="ns1:MyException"
       xmlns:ns1="http://my/ns/types">
       <message xsi:type="xsd:string">message</message>
       </MyException>
       </detail>
       </soapenv:Fault>
       </soapenv:Body>
      </soapenv:Envelope>
      
      


      The custom Exception is in the Message and the Namespace for the
      package mapping is right. But this Messag is different to the Message from the testsuite Exception example. If the Tag where like the Example, the Tag
      <MyException ...> ... </MyException>

      had to be
      <ns1:MyException ...> ... </ns1:MyException>


      And there is no "xsi:type" Attribute in the Example.

      Thanks for any hint.