sca-bindings message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [sca-bindings-comment] Comments on binding specs
- From: Simon Holdsworth <simon_holdsworth@uk.ibm.com>
- To: sca-bindings-comment@lists.oasis-open.org
- Date: Fri, 6 Nov 2009 14:11:11 +0000
Thank you for your interest in the SCA Bindings specifications.
The TC welcomes your comments and has discussed them; as a result of your
comments we have one new issue. Please refer to each comment for the TC's
response.
sca-jmsbinding-1.1 spec
- In the JMS Binding Schema there is no
<request> element
The <request> element is implicitly <binding.jms> element.
For one-way scenarios, which are likely to be common with JMS applications,
always having this extra element present in the binding seems an unnecessary
overhead. We do not propose to make any changes to the specification.
- On line 198, what happens if @create
and @jndiName have values. Which takes precedence?
The lines following 198 explain the relationship between the @create attribute
and the @jndiName attribute. All cases are covered, given that the
@create attribute has a default value of "ifNotExist". Each
value of @create defines whether or not @jndiName must have a value or
not, and if a value is required, the conditions that value must satisfy.
We do not propose to make any changes to the specification.
- On line 364, for default operation selection,
is it possible for an operation to be undetermined? If so, is an error
thrown?
The algorithm as described always has a selected operation name determined,
which defaults to "onMessage" if none of the other conditions
are met. However the text in section 4 that describes the resolved
operation name does not currently cover the case where the resolved operation
name is not one of the operations in the target components interface, so
this needs to be clarified by an update to the document. The TC has
resolved to add a normative statement to indicate that an error must be
raised in this case.
sca-wsbinding-1.1 spec
- Should a default operation selection
algorithm be detailed here? Or is it assumed from other referenced specifications?
The relevant web service specifications have a way to figure out the operation.
For example the WS-Addressing wsa:Action SOAP header block so no operation
selection algorithm is required. We do not propose to make any changes
to the specification.
Simon Holdsworth
STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair
MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK
Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898
Internet - Simon_Holdsworth@uk.ibm.com
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]