Re: SOAP-JMS prep for Last Call resolution

Dear all,

Please accept my apologies - I regret that I will be unable to make the 
call on the 28th. 

I have reviewed the latest draft and have the following minor comments 


Section 2.2:  "MUST" would be a better word than "will" in the following 
sentence :
"If a given property is specified more than once on the JMS URI the last 
instance of the property will be used. "

Sections 2.2.1: and 2.2.2
Should we now use the schema types for the restricted and special SOAP/JMS 
properties priority, deliveryMode and jndiContextParameterType?  If so 
then the schema would be better modified to use explicit global types 
rather than anonymous types (see below).

Section 2.2.1
The type for soapjms:jndiContextParameter should be (soapjms:
jndiContextParameterType) instead of (xsd:anyURI)

Section 2.2.2
The type for soapjms:deliveryMode should be (soapjmsdeliveryModeType) 
instead of (xsd:string) 
The type for soapjms:priority should be (soapjms:priorityType   ) instead 
of (xsd:int) 


Appendix Schema changes 
The priority,and jndiContextParameterType now defined as follows: 

  <xs:element name="jndiContextParameter" 
type="soapjms:jndiContextParameterType"/>
   <xs:complexType name="jndiContextParameterType">
     <xs:simpleContent>
       <xs:extension base="xs:string">
         <xs:attribute name="name" type="xs:string" use="required"/>
       </xs:extension>
     </xs:simpleContent>
   </xs:complexType>

  <xs:element name="priority" type="soapjms:priorityType"/>
    <xs:simpleType  name="priorityType">
      <xs:restriction base="xs:int">
        <xs:minInclusive value="0"/>
        <xs:maxExclusive value="9"/>
      </xs:restriction>
    </xs:simpleType>


Regards
Mark
Mark Phillips. IBM WebSphere MQ/ESB Technical Strategy - Clients & APIs






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