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: NEW ISSUE: Missing normative statements for binding.jca inboundOperation



TARGET: SCA JCA Binding Specification CD-03

DESCRIPTION:

The following attributes of binding.jca have defined behaviour, but no normative statements:

/binding.jca/inboundOperation/@name -  nothing normative to say that this must match the name of an operation in the interface (although that's the same as with the JMS binding)
/binding.jca/inboundOperation/@nativeOperation - nothing normative to say that this needs to be unique within this binding instance (cf. JMS binding selectedOperation and note different naming).  Also no normative rules about the relationship between the nativeOperation and the values returned by the operationSelector.

PROPOSAL:

Rename the nativeOperation attribute to "selectedOperation" to be consistent with binding.jms and the operation selector.

Add the following to the definition of the binding.jca/ inboundInteraction/inboundOperation/operation/@name  attribute:

The value of the inboundInteraction/inboundOperation/operation/@name attribute MUST match the name of one of the operations in the containing service's or reference's interface. [BJC200XX]

Add the following to the definition of the binding.jca/ inboundInteraction/inboundOperation/operation/@selectedOperation  attribute:

The value of the inboundInteraction/inboundOperation/operation/@selectedOperation attribute MUST be unique across the inboundInteraction element. [BJC200XX]

Add to section 4 "Operation Selectors and Wire Formats":

When a service with a JCA binding receives a message, the SCA runtime resolves the name of the operation in the service's interface that is to be invoked by using the operationSelector and inboundInteraction elements defined for the binding. The resolved operation name is defined as follows:
•        If the selected operation name generated by the operationSelector matches the value of an inboundInteraction/inboundOperation/@selectedOperation attribute then the resolved operation name is the value of the inboundInteraction/inboundOperation/@name attribute.
•        Otherwise the resolved operation name is the selected operation name generated by the operationSelector.
When a message is received at an SCA service with JCA binding, the SCA runtime MUST invoke the target component using the resolved operation name [BJC400XX].
When a message is received at an SCA service with JCA binding and the resolved operation name is not in the target component's interface the SCA runtime MUST raise an error [BJM400XX].

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








[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]