Assuming I understand this correctly, this doesn't work.
The way I have things now works: I can throw my
exceptions at the service and catch them as my exceptions
and read 'minorCode' and 'majorCode' at the client.
When I try to set this up, wsdl2java creates the
following classes:
public cla
I've included a fault response and excerpts from the WSDL
below. Will .NET and other implementations understand
this fault? If not, what do I need to do to get something
that most implementations will understand?
Note that the faultstring in the response below is empty.
However, I'll provide a
Please comment on this pseudocode for exception handling.
The majority of the client and server code would throw
subclasses of DetailedException, which would not be axis-
specific. That would be converted to and from an
AxisFault, and a generic fault would be sent over the
wire (illustrated at
Will non-Axis implementations handle the SOAP message in
Listing 7 here:
http://www-106.ibm.com/developerworks/xml/library/ws-
tip-jaxrpc.html
If so, is the technique described in the article the best
way to handle exceptions?
I'd like to be able to send a message back that my client
would
