NEW ISSUE: no priority rules for JCA binding URI and elements

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

TARGET: SCA JCA Binding Specification
CD-03

DESCRIPTION: 

The JCA binding allows the connection
factory or activation spec JNDI name to be specified as the value of the
URI attribute.  In that case, this presumably clashes with the resources
identified by the inboundConnection/activationSpec or outboundConnection/connection
elements, so the binding spec needs to define which takes precedence, and
which attributes/subelements are still honoured when the URI value is specified
(if that takes precedence).

PROPOSAL:

In outline, I think the @uri should
take precedence, and if specified this is implicitly a @create="never"
case (consistent with JMS binding), and in that case the name of the inboundConnection/activationSpec
or outboundConnection/connection element is ignored, but the resource should
still match the type if it is specified.

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