Exceptions are special, as they go back over the wire as soapfaults, the intent being better interop.
1. look at what the JAX-RPC spec has to say 2. look at AxisFault and how exceptions are handled. You will probably have to sublcass AxisFault or java.rmi.RemoteException for anything to work ----- Original Message ----- From: "Hicks, SJC (Steve) " <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 12, 2002 9:35 AM Subject: (Chained) Exceptions and beanMapping > > I've created a custom exception in WSDL with some extra fields in it, > generated the Java and deployed it all successfully (including setting up a > beanMapping), but the extra fields don't seem to be serialized and > deserialized to XML. The generated exception class has all the right > constructors and allows me to set the fields in the object, but they are not > passed in the SOAP message at all. The schema definition for the exception > is: > > <schema ...> > ... > <complexType name="MyChainedException"> > <sequence> > <element name="chainedException" nillable="true" > type="mce:MyChainedException"/> > <element name="message" nillable="true" type="xsd:string"/> > </sequence> > </complexType> > <element name="MyChainedException" nillable="true" > type="tns1:MyChainedException"/> > </schema> > > Is there something *extra* I need to do to force it to use the Bean > (De)Serializer? Is it possible to do this at all for an exception? Anyone > else had any success using chained exceptions with Axis? > > Cheers, > > Steve >
