Hi, I've seen a few threads on exception handling but nothing really concrete... The code I am attempting to wrap with a web service throws custom exceptions. Right now, I am just passing those exceptions onto AXIS and everything seems to be working well enough (i.e. a fault message is sent back to the client where the faultCode is 'Server.userException' and the faultString is the exception's message). However, lacking any real-world experience with WS/SOAP/etc, I'm concerned that these faults aren't going to be all that useful to non-java clients (unless all they do is exit or log a message when any faults occur). What I am wondering is if I want to be a little more specific with the faultCode/faultString, should I be catching these app-specific exceptions and wrapping them in an AXISFault exception? Is there something else I should be doing which perhaps doesn't require me to bring in AXIS-specific code? Ideally, I would be able to return something useful to non-java clients whi! le at the same time giving java clients everything they need to deserialize the exception so that it can be used just like an exception that was generated locally. Is this even possible? If so, can somebody give me some pointers? Thanks much.
-- Paul
