Proposed resolution to issue BINDINGS-48

[Simon Holdsworth <simon_holdsworth@uk.ibm.com>]

Folks,

My proposal to resolve issue BINDINGS-48
is as follows:

Remove the last paragraph of section
3 that describes limitations on binding attribute and intent combinations.

Replace section 5, policy, with the
following text:

The JMS binding provides attributes
that control the sending of messages, requests from references and replies
from services.  These values can be set directly on the binding element
for a particular service or reference, or they can be set using policy
intents. An example of setting these via intents is shown later.

JMS binding implementations MUST support
the JMS intent. This intent MUST always be included in the @alwaysProvides
attribute of the JMS bindingType.

The following standard intents can also
be supported by JMS binding implementations, by inclusion in the @mayProvides
attribute of the JMS bindingType:

o   atLeastOnce
o   atMostOnce
o   ordered

The atLeastOnce, atMostOnce and ordered
intent are defined in the SCA Policy Specification document in section
8, "Reliability Policy".

Deployers/assemblers can configure NON_PERSISTENT
for @JMSDeliveryMode in order to provide higher performance with a decreased
quality of service. A binding.jms element configured in this way cannot
satisfy the "atLeastOnce" policy intent. The SCA runtime MUST
raise an error for this invalid combination at deployment time.

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

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