Details

    • Release Notes Text:
      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.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW
    • Target Release:

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rdickens Russell Dickenson
                  Reporter:
                  asoldano Alessio Soldano
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: