[
https://issues.apache.org/jira/browse/CXF-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Ma resolved CXF-4847.
-------------------------
Resolution: Fixed
> Data types not correctly published in WSDL from Exception classes
> -----------------------------------------------------------------
>
> Key: CXF-4847
> URL: https://issues.apache.org/jira/browse/CXF-4847
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 2.4.10, 2.5.6, 2.6.3, 2.7.0
> Reporter: mustafa
> Assignee: Jim Ma
> Fix For: 2.8.0, 2.7.4, 2.6.7, 2.5.10
>
> Attachments: CXF4847.proposed.patch
>
>
> 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>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
