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

[JBossWS] SAAJ implementation does not set the correct NS prefix in SOAP header and body elements

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.0
    • Fix Version/s: EAP_EWP 5.1.1
    • Component/s: Web Services
    • Labels:
      None
    • Environment:

      JBoss EAP 4.3.0.GA_CP07
      JBossWS 2.0.1SP07
      JBossWS 3.3.1GA

      Description

      The SAAJ implementation in the JBossWS libraries is forcing all SOAP-nodes to have the same prefix as the <Envelope> node.
      With current native saaj implementation to create soap message from this string :
      <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><S:Header xmlns:S='http://schemas.xmlsoap.org/soap/envelopes'></S:Header><S:Body xmlns:S='http://schemas.xmlsoap.org/soap/envelopes'> <ns1:addItemResponse xmlns:ns1='http://org.jboss.ws/addressing/replyto'> <result>Mars Bar</result> </ns1:addItemResponse> </S:Body></env:Envelope>

      The created soap header and soap body are with prefix "env" . This caused some problem when ws security is enabled and soap header or body part is signed.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jim.ma Jim Ma
                  Reporter:
                  jiangshan.zhang Jiangshan Zhang
                  Writer:
                  Misty Stanley-Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: