-
1. Re: SOAPFault instead of custom Exception
sonic-dre Aug 25, 2005 5:03 AM (in response to sonic-dre)Hi again
The differences between my SOAP Message and the Testsuite Example,
causes of the fact by using "rpc encoding" instead of "rpc literal". So I try it with "rpc literal". Now my SOAP Message is equal to the Testsuiteexample.
But my Jaxrpc Client, with a jwsdp 1.5 implementation, get only the
SOAPFaultException not the custom Exception.
Why does my Client not map the SOAPFault to my custom Exception
and throw it? -
2. Re: SOAPFault instead of custom Exception
sonic-dre Aug 25, 2005 6:59 AM (in response to sonic-dre)I use for my Webservice Client a Jaxrpc DII, and now I read that the javax.xml.rpc.ServiceFactory has no notion of WS4EE deployment
Artifacts like my jaxrpc-mapping.xm.
So could it be, that my Client have no onformation about how to map my custom Exception?
Or can my Client findout the maping information by the WSDL File? -
3. Re: SOAPFault instead of custom Exception
thomas.diesler Aug 25, 2005 7:27 PM (in response to sonic-dre)The WSDL has no notion of java. Your client needs the jaxrpc-mapping.xml either through propriatary API
http://wiki.jboss.org/wiki/Wiki.jsp?page=WSClientDII
or better through a WS4EE client deployment.