RE: Soap Fault Explanation

[Cory Wilkerson]

This question has been asked time and again and I've yet to see a real definitive 
answer come through.  For starters, you might want to try some of the Axis nightly 
drops, I've had better luck with them serializing my exceptions.

In the case where I have exceptions working, I've subclassed exception and according 
to the jax-rpc specification (I don't know if Axis pays any attention here at all with 
exceptions):

1. Provided accessors for each parameter supplied to my constructor (and conversely 
ensured that each accessor had a parameter in the constructor).
2. Ensured that the parameter type in constructor was identical to return type of 
accessor.
3. Ensured that there was only one accessor with a given return type (I actually 
cheated here though I would expect I'll see some crazy results because of it.)  

I also am not sure if Axis appropriately generates fault elements in your WSDL based 
on your exception type.  If you don't see it in the WSDL you're generating stubs 
against, you'll never see an "exception" in you client code.  

Good luck!
Cory



-----Original Message-----
From: Marco Spinetti [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 9:13 AM
To: [EMAIL PROTECTED]
Subject: Soap Fault Explanation


Hi,

I'm developing a soap web service with axis (my configuration is apache
+ tomcat with axis).

In some circumstances my web services has to create a SOAP fault which
has to be sent to the client.

I'm a a bit confused with Axis management of SOAP fault (I've tried to
read email in mailing list but without success too).

I've declared my Exception:

public class DoMyException  extends org.apache.axis.AxisFault 
implements java.io.Serializable {
    private int codice;
    private java.lang.String stringa;

    public DoMyException() {
    }

    public DoMyException(
           int codice,
           java.lang.String stringa) {
        this.codice = codice;
        this.stringa = stringa;
    }
.......
 }

In my web services method, in some circumstances, I throw such
exception:

public MySearchResult doMySearch(java.lang.String query) throws
java.rmi.RemoteException, DoMyException {
        
        ......

        try {
                if (cond) {
                        throw new DoMyException(1, "Description");
                }
        }
        catch (DoMyException e) {
                ......          
                throw e;
        }
.....
}


When in my test client I try to generate a SOAP fault I don't receive
anything. With SOAPMonitor I see the request SOAP message but not the
response.

My client:

try {
       MySearchService service = new MySearchServiceLocator();
       MySearchPort port = service.getMySearchPort(); 

        .........
       MySearchResult r = port.doMySearch(query);

        .....
}
catch (DoMyException e) {
     System.err.println("Cod  = " + e.getCodice());
     System.err.println("String = " + e.getStringa());
     System.exit(1);
}


Probably I'm making some mistakes but I don't see where.

Any help would be very useful.

Thanks


Bye

--Marco