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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.1
    • EAP_EWP 5.1.0
    • Web Services
    • None

    • 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.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-4552 Release and upgrade JBossWS Native

          • 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
          clones

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-5700 CLONE - [JBossWS] SAAJ implementation does not set the correct NS prefix in SOAP header and body elements

          • 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.
          • Resolved
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBWS-3159 SAAJ implementation does not set the correct NS prefix in SOAP header and body elements

          • 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

              rhn-engineering-ema Jim Ma
              jiangshan.zhang Jiangshan Zhang (Inactive)
              Misty Stanley-Jones Misty Stanley-Jones (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: