[CXF-4847] Data types 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: 22/Feb/13 10:24
• Updated: 02/May/13 02:30
• Resolved: 05/Mar/13 07:53

Description

Fixes for CXF-4542 and CXF-4542 introduced this regression where an Exception class with a Collection was always represented as the Collection type instead of the Paramatized Type.

Example:

@WebFault
public class CustomException extends Exception {

private 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

• is cloned by: CXF-4874 Data types for Fields not correctly published in WSDL from Exception classes
• is depended upon by: CXF-4874 Data types for Fields not correctly published in WSDL from Exception classes