That would really hamper re-usability wouldnt it?
what if i needed to web service enable existing components? it would mean
(atleast) re-writing all exception classes.
there must be a better way ... if there isnt ... well ... then it should be
added.
- vikram rajan
> ----------
> From: Micael Ericsson (QIN)
> Reply To: [EMAIL PROTECTED]
> Sent: Monday, September 10, 2001 2:52 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Exception handling
>
> You should only throw SOAPException's from Java class representing a SOAP
> service. SOAPExceptions are translated into SOAP Fault codes and text. You
> can also incorporate your 'UnknownUserException' into a SOAPException.
>
> /Micael E.
>
> -----Original Message-----
> From: Vikram Rajan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 10, 2001 11:14 AM
> To: '[EMAIL PROTECTED]'
> Subject: Exception handling
>
>
> Doesnt Apache SOAP toolkit handle application-level exceptions?
>
> i.e., if I have a method with the following signature:
>
> public User getUserDetails(String id) throws UnknownUserException
>
> and the UnknownUserException is thrown by the method, shouldn't this
> exception be wrapped into a Fault object and sent across to the client?
> ...
> doesnt seem to be happening. All I get is a "null".
>
> Am using Apache SOAP 2.1 with Weblogic.
>
> any ideas? am i missing something?
>
> - vikram rajan
>
