Hello all,

I use Axis 1.1 and would like to work with custom exceptions. I generated
the client side code with wsdl2java, and the generated client stub
correctly declares these exceptions, but unfortunately the deserialization
doesn't seem to work: I get an AxisFault instead of my self-defined
exception class. It lists the class name of my exception in the message
string, but that's not what I want, of course - I'd like to receive my own
exception type on the client side.

AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: com.pegas.lpe.ExampleException: This is an example exception
 faultActor:
 faultNode:
 faultDetail:
      {}com.pegas.lpe.ExampleException: null

This "ExampleException" is directly derivated from java.lang.Exception and
contains only one constructor (with a message String as argument) and no
additional fields or methods. I tried to declare a bean mapping for the
exception in the WSDD file, but this seems to have no influence at all.

What am I doing wrong? Does the exception class need to meet some special
conventions? Do I need to to do something special, additionally to
declaring and throwing the exception in my service implementation class?
I'd like to avoid derivating the exception class from AxisFault,
RemoteException etc., it should stay independent of the underlying
technology.

Many thanks in advance for your help!

Regards,
Peter Landmann

__________________________________________
Peter Landmann
e-Business Services
System Engineer
Tel.: +49 89 898157-85
Fax: +49 89 898157-49
mailto:[EMAIL PROTECTED]
__________________________________________
PEGAS systemhaus gmbh
Rudolf-Diesel-Str. 1
D-82166 Gräfelfing
http://www.pegas.com/
http://www.e-integrator.de/
__________________________________________



Reply via email to