Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-4748

getMessage from java.lang.Throwable is excluded from accepted method

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.6.6, 2.7.3
    • JAXB Databinding
    • None
    • Unknown

    Description

      According to jax-ws spec:

      For each getter in the exception and its superclasses, a property of the same type and name is added to
      the bean. All the getter methods except getMessage from java.lang.Throwable type hierarchy
      are excluded from the list of getters to be mapped.

      But currently, message does not show up in generated wsdl in CXF:

      public class AddNumbersException extends Exception {
      private static final long serialVersionUID = 4629689348515005826L;
      String detail;

      public AddNumbersException(String message, String detail)

      { super(message); this.detail = detail; }

      public String getDetail()

      { return detail; }

      }
      <xs:complexType name="AddNumbersException">
      <xs:sequence>
      <xs:element name="detail" nillable="true" type="xs:string"/>
      </xs:sequence>
      </xs:complexType>

      The corrected version should be:
      <xs:complexType name="AddNumbersException">
      <xs:sequence>
      <xs:element name="detail" nillable="true" type="xs:string"/>
      <xs:element name="message" nillable="true" type="xs:string"/>
      </xs:sequence>
      </xs:complexType>

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dkulp Daniel Kulp
            irisding Iris Ding
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment