Alternative proposal for BINDINGS-140

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

Folks,

As discussed on Thursday here's the
alternative proposal for BINDINGS-140, using a separate type for JMS user
properties.

Outline:

Add a new JMSUserProperty type, with
an enumeration of the 8 possible type attribute values. This type is used
only for properties defined as children of the Headers type, all other
properties use the existing BindingProperty type.
Update pseudo-schema for this type,
and also fix pseudo-schema for existing errors with respect to the BindingProperty
type.

Note: this proposal is not backward
compatible.  
Note also that this proposal will require
a change to the 2 JMS test cases which have JMS user properties defined;
no change to the TA or TestCase document would be required.

Detail:

Applies to sca-jmsbinding-1.1-spec-cd04-rev2.pdf:

Update pseudo-schema to fix properties
elements of BindingProperty type to indicate that the type attribute is
a string, replacing:

<property name=”NMTOKEN” type=”NMTOKEN”?>*

by

<property name=”NMTOKEN” type=”string”?>*

on lines 77, 81, 85, 91, 95, 99, 105,
116, 120.

Update pseudo-schema to fix properties
elements of new JMSUserProperty type, replacing:

<property name=”NMTOKEN” type=”NMTOKEN”?>*

by:

<property name=”NMTOKEN” type=”boolean or byte
or .. or String”?>*

on lines 112, 125.

Update section 3.2 to add a paragraph
after the initial paragraph (at line 320):

The type of the JMS user property is
specified via the property/@type attribute using one of the values define
in the JMS specification: "boolean", "byte", "short",
"int", "long", "float", "double",
or "String" (the default).

Update JMS binding schema in Appendix
A to add the following:

<simpleType name="JMSUserPropertyType">
   <restriction
base="string">
      <enumeration
value="boolean"/>
      <enumeration
value="byte"/>
      <enumeration
value="short"/>
      <enumeration
value="int"/>
      <enumeration
value="long"/>
      <enumeration
value="float"/>
      <enumeration
value="double"/>
      <enumeration
value="String"/>
   </restriction>
</simpleType>

<complexType name="JMSUserProperty">
   <simpleContent>
      <extension base="string">
         <attribute name="name"
type="NMTOKEN" use="required"/>
         <attribute name="type"
type="sca:JMSUserPropertyType" 
               
    use="optional" default="String"/>
      </extension>
   </simpleContent>
</complexType>

Update the definition of the JMSHeaders
type to use the JMSUserProperty type - replace lines 896/897:

<element name="property" type="sca:BindingProperty"
minOccurs="0" maxOccurs="unbounded"/>

by:

<element name="property" type="sca:JMSUserProperty"
minOccurs="0" maxOccurs="unbounded"/>

Update TestCases_BJM\BJM_3025_1\src\main\resources\Test_BJM_3025_1.composite:
 replace all property elements which have type="xs:..."
to remove the "xs:".

Update TestCases_BJM\BJM_3025_2\src\main\resources\Test_BJM_3025_2.composite:
 replace all property elements which have type="xs:..."
to remove the "xs:".

Regards, Simon

Simon Holdsworth
STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair,
AT&T and Boeing Lab Advocate
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