cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mustafa (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-4847) Data types not correctly published in WSDL from Exception classes
Date Fri, 22 Feb 2013 10:28:13 GMT

     [ https://issues.apache.org/jira/browse/CXF-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

mustafa updated CXF-4847:
-------------------------

    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>
</xs:complexType>
</xs:complexType>

  was:
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"/> type="tns:myData"/>
</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>
</xs:complexType>
</xs:complexType>

    
> 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
>         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>
> </xs:complexType>
> </xs:complexType>

--
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

Mime
View raw message