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: [sca-bindings] ISSUE-67: JMS URI vs. binding attributes/elements


Logged as: http://www.osoa.org/jira/browse/BINDINGS-67

-Eric.

Simon Holdsworth wrote:
OF4D948A71.94EC1AF5-ON8025754D.0035BD78-8025754D.003E2500@uk.ibm.com" type="cite">
TARGET: jms binding cd01-rev4

DESCRIPTION:

The JMS Binding spec currently has conformance statements for attributes and elements that may potentially appear in the uri.

In assembly cd02 Section 5.1.3, line 921 on:

If a binding element has a value specified for a target service using its @uri attribute, the binding element MUST NOT identify target services using binding specific attributes or elements. [ASM50015]

Additional clarity is needed because the JMS uri spec includes values that define the target, but also includes values that assist in connecting to the messaging infrastructure, and values that influence the headers in messages that are sent to the target.

PROPOSAL:

  • Explicitly say that it is permissible to use the URI form on the JMS binding in combination with attributes and elements that define message header values and JNDI context values.  
  • Allow these values to be present in the URI and the binding, with the URI values taking precedence.
    Based on the position that if values are specified in the URI, then that is because the service is saying that those values MUST be set that way for the service to work.  So that means either the URI values take precedence, or we say the values cannot be present in the binding element.   The former case is a bit more flexible in that we can change the URI without having to also update the binding element, so my preference would be to allow both but have the URI values take precedence.
  • Include explicit statements that the destination, connectionFactory and activationSpec elements, MUST NOT be used in combination with the URI.
  • Clarify that the use of the URI form is expected to be the case where the resources already exist, i.e. there is an implicit create="never" for the resources referred to in the @uri attribute.

Specific resolution text is required if this direction is acceptable to the TC.


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]