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

    • 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

      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.

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

              Created:
              Updated:
              Resolved: