See JSR 101 version 1.0 chapter 4.3.6 The mapping fo WSDL faults has
changed several times during the development of the specification.
If you still think that the Axis is in error, please open a bugzilla
defect.
Thanks,
Rich 'Shirley' Scheuerle
IBM WebSphere & Axis Web Services Development
512-838-5115 (IBM TL 678-5115)
"Milos Cekovic" <[EMAIL PROTECTED]>
07/17/2002 04:02 AM
Please respond to axis-user
To: [EMAIL PROTECTED]
cc:
Subject: fault message
Hi,
In beta2 WSDL2Java generates for each fault in a portType a class that
extends AxisFault. This class is thrown from a service call.
Since beta3 WSDL2Java does not generate this class. It just throws
a ComplexType that is a part of a fault message which results in
compilation
errors.
Here is the portType definition:
<portType name="SrvDataDictionaryPortType">
<operation name="getDataDictionary">
<input message="..."/>
<output name="..."/>
<fault name="getDataDictionaryException" message
="datadict:DataDictionaryFault"/>
</operation>
...
And the message is:
<message name="DataDictionaryFault">
<part name="exception" type="mytypes:ArrayOfMyError"/>
</message>
The array is defined as:
<complexType name="ArrayOfMyError">
<complexContent>
<restriction base="soapenc:Array">
<sequence>
<element name="item" minOccurs="0" maxOccurs="unbounded" type
="mytypes:MyError"/>
</sequence>
<attribute ref="soapenc:arrayType"
soapenc:arrayType="mytypes:MyError
[]"/>
</restriction>
</complexContent>
</complexType>
And its elements as:
<complexType name="MyError">
<all>
<element name="code" type="xsd:string"/>
<element name="message" type="xsd:string"/>
</all>
</complexType>
In beta2 WSDL2Java generated a DataDictionaryFault class that extends
AxisFault.
In beta3 there s no such class, but in PortType.java service throws it!
Is it a bug in WSDL2Java?
Do you have some workarounds?
Thanks in advance.
Milos Cekovic
Basel, Switzerland
