Re: [sca-bindings] Updated proposed resolution for BINDINGS-67

Revised proposal folding in a) and b)
from Dave's suggestions.

Note that I deliberately did not include
normative text in the statement "If the @uri attribute includes a
value for this attribute then the @uri value is used and this attribute
is ignored. " because there is already a normative statement that
covers this in the @uri attribute definition.  We would end up with
three conformance statements saying the same thing, that the @uri values
take precedence over the binding attributes and elements.

-----------------------

Update the last sentence of the current definition of
binding.jms/@uri: 

"i.e. there is an implicit @create="never" for the resources
referred to in the @uri attribute." 

Add to the definition of the binding.jms/@uri attribute:

When the @uri attribute is specified, the destination element MUST NOT
be present.

An SCA runtime MUST use the values specified in the @uri attribute in preference
to corresponding attributes and elements in the binding.

Replace the last sentence of the ConnectionFactory element:

  When the connectionFactory element
is present, then the destination MUST be defined either by the destination
element or the @uri attribute 

Replace the sentence in the ActivationSpec element:

  If a destination is also
specified via a destination element or the @uri attribute it MUST refer
to the same JMS destination as the activationSpec

Replace the following sentence from description of binding.jms/headers/@JMSType...
etc. 

  The value of the @uri
attribute MUST NOT include values for these properties if they are specified
using these attributes. 

by: 

  If the @uri attribute includes values
for these attributes then the @uri values are used and these attributes
are ignored. 

Replace the following sentence from description of binding.jms/subscriptionHeaders/@JMSSelector:

  The value of the @uri
attribute MUST NOT include values for this property if it is specified
using this attribute. 

by: 

  If the @uri attribute includes a value
for this attribute then the @uri value is used and this attribute is ignored.

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 - 

David Booz <>

11/02/2009 14:24

To



cc

Subject

Re: [sca-bindings] Updated proposed
resolution for BINDINGS-67

A few suggested re-wordings:

a)

i.e. there is an implicit @create="never" for the resources referred
to in the @uri attribute.

b)

When the @uri attribute is specified, the destination element MUST NOT
be present.

c) 

If the @uri attribute includes values for
these attributes then the @uri values are used and these attributes MUST
be ignored.

d)

same change to proposed JMS Selector text.

Dave Booz

STSM, BPM and SCA Architecture

Co-Chair OASIS SCA-Policy TC and SCA-J TC

"Distributed objects first, then world hunger"

Poughkeepsie, NY (845)-435-6093 or 8-295-6093

e-mail:

Simon
Holdsworth ---02/11/2009 06:13:01 AM---Folks, Updated resolution, based
on the assertion that it is only the Destination

From:

Simon Holdsworth <>

To:



Date:

02/11/2009 06:13 AM

Subject:

[sca-bindings] Updated proposed resolution for BINDINGS-67

Folks, 

Updated resolution, based on the assertion that it is only the Destination
that defines the "target" of binding.jms:

Update the last sentence of the current definition of binding.jms/@uri:

"i.e. there is an implicit create="never" for the resources
referred to in the @uri attribute." 

Add to the definition of the binding.jms/@uri attribute:

When the @uri attribute is specified, the binding.jms MUST NOT also include
a destination element. 

An SCA runtime MUST use the values specified in the @uri attribute in preference
to corresponding attributes and elements in the binding.

Replace the last sentence of the ConnectionFactory element:

. When the connectionFactory element is present,
then the destination MUST be defined either by the destination
element or the @uri attribute 

Replace the sentence in the ActivationSpec element:

. If a destination is also specified
via a destination element or the @uri attribute it MUST refer to the same
JMS destination as the activationSpec

Replace the following sentence from description of binding.jms/headers/@JMSType...
etc. 

The value of the @uri attribute
MUST NOT include values for these properties if they are specified using
these attributes. 

by: 

If the @uri attribute includes values for
these attributes then the @uri values are used and these attributes are
ignored. 

Replace the following sentence from description of binding.jms/subscriptionHeaders/@JMSSelector:

The value of the @uri attribute
MUST NOT include values for this property if it is specified using this
attribute. 

by: 

If the @uri attribute includes a value for
this attribute then the @uri value is used and this attribute is ignored.

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 

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