|
I have a web
service that I am trying to migrate from Axis1 to Axis2. The service
is deployed as a POJO and I throw a custom checked exception from some
of my methods. The exception shows up in the WSDL that is auto
generated by Axis:
<xs:complexType name="AuthenticatorException"> <xs:complexContent> <xs:extension base="ns:Exception"> <xs:sequence> <xs:element minOccurs="0" name="multiException" nillable="true" type="xs:anyType"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> The "multiException" element, in Java, is a list of other custom exceptions that don't currently show up in the wsdl. The issue I am having is AuthenticatorException is sent back as a fault that is not filled in: <?xml version='1.0' encoding='utf-8'?> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"> <soapenv:Body> <soapenv:Fault> <soapenv:Code><soapenv:Value>soapenv:Receiver</soapenv:Value></soapenv:Code> <soapenv:Reason><soapenv:Text xml:lang="en-US">Multiple authentication exceptions.</soapenv:Text></soapenv:Reason> <soapenv:Detail /> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> In Axis1, I used <beanMapping> in the server-config.wsdd to make sure that the custom exceptions were serialized properly when they were thrown out of my web service. Since that doesn't exist in Axis2, how can I get my exceptions to serialize properly in the soap fault? Even if AuthenticatorException has a simple string element, nothing is sent back in the SOAP fault. Is there an example somewhere of sending back a custom soap fault like this? Thanks Tony This message (and any associated files) is intended only for the
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Stoneware, Inc. may be monitored. |
