OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: NEW ISSUE: no defaults for JMS headers



Folks,

Given that this issue is effectively raised as a result of the public review comment in BINDINGS-100, and that it is potentially the only issue, we could consider resolving this issue as part of the resolution of BINDINGS-100 and not open a separate issue for it.

Regards, Simon

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


__________________

TARGET: SCA JMS Binding Specification CD-03

DESCRIPTION:

The JMS binding does not define default values for the deliveryMode, priority and timeToLive attributes.  The lack of default values affects portability of binding definitions, potentially resulting in quite different behaviour of the same binding definition on different SCA runtimes.

PROPOSAL:

Update the defaults for these values to match the JMS API defaults.  Note that the "type" header has no defined values and therefore default is unspecified.

For the pseudo-schema element  /binding.jms/headers/@type, @deliveryMode, @timeToLive, @priority  Update the last paragraph to:   Valid values for @deliveryMode are “persistent” and “nonpersistent” with "persistent" being the default; valid values for @priority are “0” to “9”, with "4" being the default; valid values for @timeToLive are positive integers, with 0 indicating unlimited time and being the default value.

There is no need to update the definition of the operationProperties/headers attributes as if these are not specified they default to the values specified in the headers element, which provides the defaults if not specified at that level either.

In the XML schema, update the deliveryMode, timeToLive and priority attribute definitions to include default values:

<attribute name="deliveryMode" default="persistent">
<simpleType>
<restriction base="string">
<enumeration value="persistent"/>
<enumeration value="nonpersistent"/>
</restriction>
</simpleType>
</attribute>
<attribute name="timeToLive" type="long" default="0"/>
<attribute name="priority" default="4">
<simpleType>
<restriction base="string">
<enumeration value="0"/>
<enumeration value="1"/>
<enumeration value="2"/>
<enumeration value="3"/>
<enumeration value="4"/>
<enumeration value="5"/>
<enumeration value="6"/>
<enumeration value="7"/>
<enumeration value="8"/>
<enumeration value="9"/>
</restriction>
</simpleType>
</attribute>


Regards, Simon

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












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]