Hi,

I have a question on how Axis 1.1 generates a user-defined fault through the WSDL2Java tool. I have defined a schema for an exception I want to return whenever something wrong happens during Web Service processing. In my custom WSDL, I specified this exception in the message, portType and binding definitions. When I use the WSDL2Java tool to generate the server-side skeleton, I do not see this exception in any throws clause or defined anywhere except in the deploy.wsdd file. The Exception class gets generated properly from the schema but does not look like Axis knows how to put this into the service. I have attached portions of my code below. Any advice would be appreciated. Thanks!

-los

#### Schema ####
....
   <xsd:element name="ProcessingFault" type="ProcessingProblemType"/>

<xsd:complexType name="ProcessingProblemType">
<xsd:sequence>
<xsd:element name="exceptionMessage" type="xsd:string" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
....
##############


### WSDL ####

<!-- message definitions -->
....
   <message name="DownloadError">
        <part name="error" element="fault:ProcessingFault"/>
   </message>

<!-- port type definitions -->
   <portType name="DownloadPortType">
       <operation name="downloadPrograms">
        ....
            <fault name="ProcessingProblemMessage" message="tns:DownloadError"/>
       </operation>
   </portType>


<!-- binding definitions --> ... <fault name="ProcessingProblemMessage"> <soap:fault name="ProcessingProblemMessage" use="literal"/> </fault>

############

_________________________________________________________________
Get ready for school! Find articles, homework help and more in the Back to School Guide! http://special.msn.com/network/04backtoschool.armx




Reply via email to