[AXIS-2799] Problem in generation of java code using wsdl2java in Axis

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: WSDL processing
• Environment: Axis1 release
• Assignee: Unassigned
• Reporter: Pradeep Selvaraj
• Created: 30/Jul/09 14:23
• Updated: 30/Jul/09 14:23

Description

We started using Axis for our project recently.
There is a major difference in the way exception classes are generated by Axis when compared with other frameworks. Our Sample WSDL file
defines 6 elements of type MessagingFaultDetail and also tags those 6 elements as faults in the definition of different requests.

WSDL:

<xsd:complexType name="MessagingFaultDetail">
<xsd:sequence>
<xsd:element minOccurs="0" maxOccurs="1" name="detailMessage" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="MessagingFault" type="types:MessagingFaultDetail"/>
<xsd:element name="InvalidFormatFault" type="types:MessagingFaultDetail"/>
<xsd:element name="AuthenticationFault" type="types:MessagingFaultDetail"/>
<xsd:element name="MessageNotFoundFault" type="types:MessagingFaultDetail"/>
<xsd:element name="PromptNotFoundFault" type="types:MessagingFaultDetail"/>
<xsd:element name="PromptExistsFault" type="types:MessagingFaultDetail"/>

With this WSDL file, XFire generated 6 exception classes that internally use the class MessagingFaultDetail.
But Axis generates just one exception class MessagingFaultDetail. This affects the granularity of exception handling.
This affects the way that exceptions are handled in our application.
Is it possible to configure Axis wsdl2java so that it generates exception classes similar to XFire or others?