sca-bindings message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: NEW ISSUE: JMS binding pseudo-schemas inconsistent with assembly
- From: Simon Holdsworth <simon_holdsworth@uk.ibm.com>
- To: sca-bindings@lists.oasis-open.org
- Date: Thu, 13 Mar 2008 11:45:51 +0000
Title: JMS binding pseudo-schemas inconsistent with
assembly
Target: binding.jms
Description:
The current pseudo-schema definition for binding.jms
includes "string" types for attributes that have a fixed set
of values, with those values being enumerated in the definition of the
attribute. In assembly, the approach that is taken is to enumerate
those values in the pseudo-schema, so for example binding.jms currently
has:
<binding.jms correlationScheme=”string”?
Whereas assembly uses the following:
multiplicity="0..1 or 1..1 or 0..n or 1..n"?
Proposal:
Update the pesudo-schema in binding.jms to enumerate options explicitly
in the pseudo-schema.
Replace definition of correlationScheme attribute
by:
correlationScheme=”RequestMsgIDToCorrelID
or RequestCorrelIDToCorrelID or None”
Replace definition of create attribute throughout
by:
create=”always or never or ifnotexist”
Replace definition of JMSDeliveryMode attribute throughout
by:
JMSDeliveryMode=”PERSISTENT or NON_PERSISTENT”
Replace definition of JMSPriority attribute throughout
by:
JMSPriority=”0 .. 9”
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]