Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5 RC2
    • Component/s: Core
    • Labels:
      None

      Description

      This will be implemented as a EndpointMapping + EndpointInterceptor. The only issue is that there are five different, incompatible versions of WS-Addressing in use today (see http://blog.springframework.com/arjen/archives/2006/07/22/ws-addressing-needs-a-phone-book/). We will probably go for the August 2004 and May 2006 (final) version, but make it pluggable so that other version can be added later.

        Issue Links

          Activity

          Hide
          magnus Magnus Heino added a comment -

          Does this mean that SoapHeaderElements will be able to have children so it's possible to generate xml like

          <wsa:From>
          <wsa:Address>foobar</wsa:Address>
          </wsa:From>

          Show
          magnus Magnus Heino added a comment - Does this mean that SoapHeaderElements will be able to have children so it's possible to generate xml like <wsa:From> <wsa:Address>foobar</wsa:Address> </wsa:From>
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          Adding children to soap header elements already works. You can add any XML to the header or header element by transforming to the Results they expose.

          Show
          arjen.poutsma Arjen Poutsma added a comment - Adding children to soap header elements already works. You can add any XML to the header or header element by transforming to the Results they expose.
          Hide
          magnus Magnus Heino added a comment -

          Ok, thats what I'm doing. But what about when I want to parse that same xml? What if <wsa:Address> has setMustUnderstand=true? Should I then leave the spring-ws abstraction, take the header xml as a string, and parse it on my own?

          Show
          magnus Magnus Heino added a comment - Ok, thats what I'm doing. But what about when I want to parse that same xml? What if <wsa:Address> has setMustUnderstand=true? Should I then leave the spring-ws abstraction, take the header xml as a string, and parse it on my own?
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          You can access the mustUnderstand attribute with the mustUnderstand property on SoapHeaderElement.

          Show
          arjen.poutsma Arjen Poutsma added a comment - You can access the mustUnderstand attribute with the mustUnderstand property on SoapHeaderElement.
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          Closing issues for 1.5.

          Show
          arjen.poutsma Arjen Poutsma added a comment - Closing issues for 1.5.

            People

            • Assignee:
              arjen.poutsma Arjen Poutsma
              Reporter:
              arjen.poutsma Arjen Poutsma
            • Votes:
              5 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: