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: resolved operation behavior overlap in BJC40001/2



TARGET: SCA JCA Binding Specification cd03-rev4

DESCRIPTION:

BJC40001 and 40002 overlap. As per BINDINGS-121 they currently state:

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 [BJC40001].

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 [BJC40002].


These overlap, in that BJC40001 is not as stated conditional on the resolved operation name being in the target components interface, although of course it is as otherwise how can the operation get invoked?

The intent was that these would be consistent with JMS, and as such were copied from the latest JMS draft.  As it happens, Issue BINDINGS-108 which changed this text in the JMS binding had been incorrectly applied.  When corrected, the JMS version of this statement does include the phrase "and the resolved operation name is in the target component's interface".

PROPOSAL:

Replace BJC40001 with the following text:

When a message is received at an SCA service with JCA binding and the resolved operation name is in the target component's interface the SCA runtime MUST invoke the target component using the resolved operation name [BJC40001].


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]