Details

    • Release Notes Text:
      This release of JBoss EAP 5 includes a fix to an issue where an Exception class used in a Web Service that used a Collection was always represented as the Collection type instead of the Paramatized Type in the generated WSDL.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      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:

      CustomException.java
      @WebFault
      public class CustomException extends Exception {
      private ArrayList<MyData> names;
      

      This is what you get using fixes from JBPAPP-10566

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

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mmusaji Mustafa Musaji
                  Reporter:
                  mmusaji Mustafa Musaji
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: