ws-woden-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Kaputin (JIRA)" <>
Subject [jira] Assigned: (WODEN-157) SOAP binding reuses HTTP properties
Date Tue, 19 Jun 2007 14:23:27 GMT


John Kaputin reassigned WODEN-157:

    Assignee: John Kaputin

> SOAP binding reuses HTTP properties
> -----------------------------------
>                 Key: WODEN-157
>                 URL:
>             Project: Woden
>          Issue Type: Bug
>          Components: Parser
>    Affects Versions: M7a
>            Reporter: Lawrence Mandel
>            Assignee: John Kaputin
> Jacek Kopecky <> reported the following Woden bug on the
W3C mailing list. See
> (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
> namespace.
> 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.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message