Proposed actions for issue BINDINGS-100

My reaction to these comments (resending
as we have now opened BINDINGS-100)

sca-jmsbinding-1.1 spec 

In the JMS Binding Schema there is no
<request> element 

Response: "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."

I don't believe we need any spec change for this one.

On line 198, what happens if @create
and @jndiName have values. Which takes precedence?

Response: "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".

I don't believe we need any spec change for this one.

On line 364, for default operation selection,
is it possible for an operation to be undetermined? If so, is an error
thrown?

Response: "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."

I think we need a spec change for this, my proposed resolution to which
would be to add a new statement to section 4 alongside BJM40010 to say:

"When a message is received at an SCA service with JMS binding, if
the resolved operation name is not in the target component's interface
the SCA runtime MUST raise an error [BJM400XX]."

I tried a variant with merging this text into the existing BJM40010 statement,
but it became too messy.

A side-note on this one, given that JMS has no fault mechanism, we can't
say that an exception is thrown or a fault returned to the caller, so we
gloss over this by saying "raise an error".

sca-wsbinding-1.1 spec 

Should a default operation selection
algorithm be detailed here? Or is it assumed from other referenced specifications?

Response: "The relevant web service specifications [referenced needed?]
have a specified algorithm for identifying the name of the operation being
invoked, so no operation selection algorithm is required."

I don't believe we need any spec change for this one.

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 - 

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