[CXF-4874] Data types for Fields not correctly published in WSDL from Exception classes

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.10, 2.5.6, 2.6.3, 2.7
• Fix Version/s: 2.7.4, 2.6.7, 2.5.10, 3.0.0-milestone1
• Component/s: JAXB Databinding
• Estimated Complexity: Unknown
• Assignee: Jim Ma
• Reporter: mustafa
• Created: 05/Mar/13 10:42
• Updated: 04/May/17 19:42
• Resolved: 11/Mar/13 08:09

Description

This fix relies on CXF-4847 and fixes the same issue described in this but for public Field Types.

Example:

@WebFault
public class CustomException extends Exception {

public ArrayList<MyData> names;
...

<xs:complexType name="CustomException">
<xs:sequence>
<xs:element name="names" nillable="true" type="tns:arrayList"/>
</xs:sequence>

But it should be

<xs:complexType name="CustomException">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="names" type="tns:myData"/>
</xs:sequence>

Issue Links

• depends upon: CXF-4847 Data types not correctly published in WSDL from Exception classes
• is a clone of: CXF-4847 Data types not correctly published in WSDL from Exception classes
• is duplicated by: CXF-5538 Parameterized Types do not work on Exception Classes