- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Mon, 14 Nov 2005 14:23:19 -0800
- To: "Jacek Kopecky" <jacek.kopecky@deri.org>
- Cc: <public-ws-desc-comments@w3.org>
Thanks for your comment. The WS Description Working Group tracked this as a Last Call comment LC333 [1]. We accepted the proposal at http://lists.w3.org/Archives/Public/www-ws-desc/2005Oct/0051.html to address this problem. As we plan to go to CR shortly, if we don't hear from you within 10 days, we will assume this satisfies your concern. [1] http://www.w3.org/2002/ws/desc/5/lc-issues/issues.html#LC333 -----Original Message----- From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-comments-request@w3.org] On Behalf Of Jacek Kopecky Sent: Tuesday, September 06, 2005 12:13 PM To: public-ws-desc-comments@w3.org Subject: WSDL 2: binding defaults not component model properties? Hi all, a last call comment on the 2005 last call draft of the adjuncts: In both bindings, SOAP and HTTP, there are a number of attributes for specifying defaults, like transferCodingDefault, mepDefault, methodDefault etc. These attributes are used when constructing the component model, but they only provide the defaults for the created operation and message reference components, for example a binding operation will get the default HTTP transfer coding if it doesn't specify its own. I don't think this will work the expected way for interfaceless bindings, i.e. bindings that don't say what interface they bind. These bindings don't contain any operations, so the defaults are not used and are dropped. I'm not sure what is used for those affected properties when the binding is used on an endpoint and thus indirectly connected to the endpoint's service's interface. I believe we should add component properties to carry these default values in the component model. Best regards, Jacek Kopecky
Received on Monday, 14 November 2005 22:24:01 UTC