Logged as: http://www.osoa.org/jira/browse/BINDINGS-122
-Eric.
On 02/22/2010 09:13 AM, Simon Holdsworth wrote:
OF4CB04669.2E3EFFDD-ON802576D2.005DC877-802576D2.005E2EE6@uk.ibm.com"
type="cite">
TARGET: SCA JCA Binding
Specification
CD-03 rev 3
DESCRIPTION:
The following elements/attributes
have
defined behaviour in the JCA binding spec, but no normative statements:
/binding.jca/outboundInteraction/operation/interactionSpec
-
the operation-level properties are stated as overriding the
binding-level
ones, but there is no normative statement to that effect (cf. JMS
binding
operationProperties).
/binding.jca/outboundInteraction/operation/@name
-
nothing normative to say that this must match the name of an operation
in the interface, or be unique.
PROPOSAL:
Add the following to the
/binding.jca/outboundInteraction/operation/interactionSpec
element description:
When an operation is invoked via a
reference
with a binding.jca element, if there is an ouboundInteraction/operation
element whose @name attribute matches the name of the operation being
invoked,
the SCA runtime MUST use the values supplied by the interactionSpec
child
of the operation element instead of the interactionSpec child of the
binding.jca
element, if any [BJC200XX]
Add the following to the
binding.jca/outboundInteraction/operation/@name
attribute description:
The value of the
outboundInteraction/operation/@name
attribute MUST be unique within the ouboundInteraction element.
[BJC200XX]
The value of the
outboundInteraction/operation/@name
attribute MUST match the name of one of the operations in the
containing
service's or references' interface. [BJC200XX]
Simon Holdsworth
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
|