Uploaded image for project: 'Woden'
  1. Woden
  2. WODEN-157

SOAP binding reuses HTTP properties


    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: M7a
    • Fix Version/s: 1.0
    • Component/s: Parser
    • Labels:


      Jacek Kopecky <jacek.kopecky@deri.org> reported the following Woden bug on the W3C mailing list. See http://lists.w3.org/Archives/Public/www-ws-desc/2007May/0001.html.

      (design) the SOAP binding reuses HTTP properties. In Woden, the
      reused properties are returned when looking at the SOAP extensions
      (for instance SOAPBindingExtensions.isHttpCookies(), and all similar
      occurrences). I believe this is counterintuitive - when I'm looking for
      the value of the

      {http cookies} property on a binding, it's defined by a
      WHTTP extension attribute and it should be available under that

      Why do I care? The RDF binding maps {http cookies}

      into the same thing
      whether it is on an HTTP binding or on a SOAP binding, and I must check
      two different extensions to get the value of this property.

      SOAPBindingExtensions.isHttpCookies(), if it's there at all, should IMHO
      be syntactic sugar for HTTPBindingExtensions.isHttpCookies() on the same
      binding, but as it is, I don't even get HTTPBindingExtensions on a SOAP
      binding. The type of a binding should not dictate the namespaces of
      allowed extensions, or under what namespaces one can find some
      properties. I don't think the spec intends that.




            • Assignee:
              jkaputin John Kaputin
              lmandel Lawrence Mandel
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: