[CXF-1127] JAXB Data Binding Generates Duplicate Fault Elements in Generated WSDL

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.2
• Fix Version/s: 2.0.3
• Component/s: JAXB Databinding
• Assignee: Daniel Kulp
• Reporter: Ronald Pieterse
• Created: 22/Oct/07 08:54
• Updated: 05/Dec/07 19:23
• Resolved: 22/Oct/07 20:18

Description

In my service I have 6 calls that can throw 3 exceptions each. In the generated wsdl file the exceptions are all duplicated, times the number of methods. In my case that will be 6 * 3 exception declarations in my wsdl.

Here's an example of a service method (they all look alike so I did just one):

@WebResult(name = "databaseFields")
public DatabaseField[] getDatabaseFields(@WebParam(name = "authInfo") AuthInfo authInfo,
@WebParam(name = "databaseName") String databaseName)
throws InvalidAuthInfoException, InvalidInputException, TripolisUnknownException;

Here's a snippet from the generated wsdl:

<xsd:schema xmlns:ns0="http://api.tripolis.com/" xmlns:tns="http://exceptions.api.tripolis.com/" targetNamespace="http://exceptions.api.tripolis.com/" attributeFormDefault="unqualified" elementFormDefault="unqualified">
<xsd:element name="InvalidAuthInfoException" type="ns0:invalidAuthInfoFault" nillable="true"/>
<xsd:element name="TripolisUnknownException" type="ns0:tripolisUnknownFault" nillable="true"/>
<xsd:element name="InvalidInputException" type="ns0:invalidInputFault" nillable="true"/>
<xsd:element name="InvalidAuthInfoException" type="ns0:invalidAuthInfoFault" nillable="true"/>
<xsd:element name="TripolisUnknownException" type="ns0:tripolisUnknownFault" nillable="true"/>
<xsd:element name="InvalidInputException" type="ns0:invalidInputFault" nillable="true"/>
<xsd:element name="InvalidAuthInfoException" type="ns0:invalidAuthInfoFault" nillable="true"/>
...
<xsd:element name="InvalidAuthInfoException" type="ns0:invalidAuthInfoFault" nillable="true"/>
<xsd:element name="TripolisUnknownException" type="ns0:tripolisUnknownFault" nillable="true"/>
<xsd:element name="InvalidInputException" type="ns0:invalidInputFault" nillable="true"/>
</xsd:schema>

This bug might be the same as https://issues.apache.org/jira/browse/CXF-745 that was presumed to be fixed.

Am I doing something wrong here? Or was the bug never fixed?