|
In the User Guide, there is a description of how to use a
wsdl:fault element to describe an Exception to a client – Exceptions
are represented as wsdl:fault elements
If a
method is marked as throwing an Exception that is
not an instance or a subclass of java.rmi.RemoteException,
then things are subtly different. The exception is no longer a SOAP Fault, but
described as a wsdl:fault in the WSDL of the
method. According to the JAX-RPC specification, your subclass of Exception must
have accessor methods to access all the fields in the object to be marshalled and a constructor that takes as parameters
all the same fields (i.e, arguments of the same name and type). This is a kind
of immutable variant of a normal JavaBean What is the default behaviour when there isn’t a
wsdl:fault in the WSDL, but an Exception is thrown? The reason I’m
asking is that all I’m getting back in my client (.NET) is a
“Invalid Namespace Declaration” message. Thanks! Jerry Jalenak Software Engineer Netopia, Inc. |
