Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.7.9
-
None
-
None
-
Unknown
Description
As part of the fix CXF-4542 we believe introduced this regression where an Exception class with a Collection was always represented as the Collection type instead of the Paramatized Type.
Example:
CustomException.java
@WebFault public class CustomException extends Exception { private ArrayList<MyData> names;
This is what you get using fixes from CXF-4542
<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>
Attachments
Attachments
Issue Links
- duplicates
-
CXF-4874 Data types for Fields not correctly published in WSDL from Exception classes
- Closed