Re: [sca-bindings] BINDINGS-93 - alternate proposal....

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

I'm OK with this alternative proposal,
as it does formalise the "unique response destination per request"
behaviour.

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

From:	Eric Johnson <eric@tibco.com>
To:	OASIS SCA Bindings <sca-bindings@lists.oasis-open.org>
Date:	30/09/2009 05:38
Subject:	[sca-bindings] BINDINGS-93 - alternate proposal....

---

It occurred to me while looking at the proposal for BINDINGS-93,
that it might be even clearer to add another predefined @correlationScheme
value, specifically that of "sca:uniqueDestination", since that
is effectively what we're requiring.

I think this means a revised proposed resolution as follows:

(Section 3, @correlationScheme definition), add the following after "sca:none"
sentence:

"If the value of @correlationScheme is "sca:uniqueDestination"
the SCA runtime MUST use a unique response destination for each request,
and there MUST NOT be a response element specified."

This:
"For an SCA reference with a JMS binding, the SCA runtime MAY choose
to receive response messages on the basis of their correlation ID as defined
by the binding’s @correlationScheme attribute, or use a unique destination
for each response [BJM60006]."

becomes:
"For an SCA reference with a JMS binding, the SCA runtime MUST correlate
response messages on the basis of binding’s @correlationScheme attribute
[BJM60006]."

(If I've not missed a point here, it would now be possible to not set a
"response" element, and use a correlation other than "sca:uniqueDestination". 
That should be fine though.  A caller can use a temporary queue multiple
times to do some number of request/response exchanges, and use a correlation
mechanism other than a unique destination.  BINDINGS-93 seems to imply
that this is not a reasonable combination, but I'm unclear on why that
would be so.)

---

Oops - typos:
Line 648: <binding.jms correlationScheme=”sca:messageId”>

Should be: <binding.jms correlationScheme=”sca:messageID”>

Likewise line 656 and 799.

I'll file an issue for these.

-Eric.

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

---

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