[jira] Commented: (WODEN-157) SOAP binding reuses HTTP properties

["John Kaputin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WODEN-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567001#action_12567001 ] 

John Kaputin commented on WODEN-157:
------------------------------------

With WODEN-47, it's possible to use the new WSDLComponent methods getExtensionProperties(extNSuri) or getExtensionProperty(extNSuri, extPropNameString), which will  return all ext props from an ext namespace or just a specific ext property.

The RDF binding could map {http cookies} by calling:

Binding.getExtensionProperty(HTTPConstants.NS_URI_HTTP, HTTPContants.PROP_HTTP_COOKIES);

....or by retrieving the set of binding ext props from the HTTP ext namespace:

Binding.getExtensionProperties(HTTPConstants.NS_URI_HTTP);

This will work regardless of whether the binding is of type HTTP or SOAP/HTTP. 

The 'static' extension API, SOAPBindingExtensions still contains the HTTP extension accessor methods that apply when the underlying protocol is HTTP, but the new 'generic' extension programming model introduced by WODEN-47 can be used instead. I think we still need to consider removing  the HTTP accessor methods from the static SOAP extension APIs because these APIs are really based on extension namespace, not binding type. If it's necessary, we could consider introducing some sort of 'binding-type' extension API, but this would need to cater for other WSDL extensions too, not just those defined by the WSDL spec (i.e. not just SOAP with a few additional HTTP properties). 

> SOAP binding reuses HTTP properties
> -----------------------------------
>
>                 Key: WODEN-157
>                 URL: https://issues.apache.org/jira/browse/WODEN-157
>             Project: Woden
>          Issue Type: Bug
>          Components: Parser
>    Affects Versions: M7a
>            Reporter: Lawrence Mandel
>            Assignee: John Kaputin
>             Fix For: M8
>
>
> Jacek Kopecky <ja...@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
> 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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org