Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10922

SOAPAction value not used for ws operation dispatch

    XMLWordPrintable

Details

    • Hide
      An issue in the JBossWS-Native component of previous versions of JBoss EAP 5 has been resolved in this release.

      The issue arose becuase the SOAPAction value was not used as a mechanism for selecting the correct WS endpoint operation for incoming messages on server side.

      This could impact encrypted messages or doc/lit bare endpoints with multiple operations with the same parameters, ws-addressing disabled and valid soapAction specified in @WebMethod annotations.

      The SOAPAction value is now correctly used for selecting the endpoint operation.
      Show
      An issue in the JBossWS-Native component of previous versions of JBoss EAP 5 has been resolved in this release. The issue arose becuase the SOAPAction value was not used as a mechanism for selecting the correct WS endpoint operation for incoming messages on server side. This could impact encrypted messages or doc/lit bare endpoints with multiple operations with the same parameters, ws-addressing disabled and valid soapAction specified in @WebMethod annotations. The SOAPAction value is now correctly used for selecting the endpoint operation.
    • Documented as Resolved Issue
    • NEW

    Description

      The SOAPAction value is erroneosly not used as a mechanism for selecting the correct ws endpoint operation for incoming messages on server side. This is relevant for example for encrypted messages or for doc/lit bare endpoints with multiple operations with the same parameters, ws-addressing disabled and valid soapAction specified in @WebMethod annotations.

      Attachments

        Issue Links

          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBPAPP-10435 Release and upgrade JBossWS-Native for EAP 5.3.0

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10905 Operation-specific WSS config doesn't get applied when SOAP body is encrypted

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rdickens_jira Russell Dickenson (Inactive)
              rhn-support-asoldano Alessio Soldano
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: