Re: [sca-bindings] Updated proposal for BINDINGS-94

[Eric Johnson <eric@tibco.com>]

One comment here - I don't know if anyone cares.

On 12/11/2009 02:31 AM, Simon Holdsworth wrote:

OF09238242.DDEEE0D4-ON80257689.003897F7-80257689.00398473@uk.ibm.com" type="cite">
This proposal has the proposed resolution of BINDINGS-96 as per http://lists.oasis-open.org/archives/sca-bindings/200912/msg00008.html as a prerequisite.

-------------------------------------------------

Overview:

Specify that the value of the scaCallbackDestination is a JMS URI

Over at the W3C, we were discussing a related point in the SOAP/JMS WG.

I think we agreed that for SOAP/JMS, we do not need to mandate that the URI be a "jms" URI scheme, but rather that the URI correspond to a JMS Destination, and that it SHOULD be a "jms" URI.  That way, if vendors have non-IETF standardized ways of indicating a JMS Destination, it would be possible.

What might fit the bill here?  The AMQP protocol (and an associated URI), can support JMS type interactions.  So it is possible, in the future, that someone could use an AMQP URI, but with the JMS semantics....

This is perhaps overly generous, and too pie-in-the-sky?

OF09238242.DDEEE0D4-ON80257689.003897F7-80257689.00398473@uk.ibm.com" type="cite">
Detail:

Change the definition of the "scaCallbackDestination" user property to be "a JMS URI that identifies the Destination to which callback messages are sent, in the format defined by the IETF URI Scheme for Java™ Message Service 1.0 [IETFJMS]"

The alternate text here could be:
"a URI that identifies the JMS Destination to which callback messages are sent. This SHOULD be in the format defined by the IETF URI Scheme for Java™ Message Service 1.0 [IETFJMS]"

-Eric.

OF09238242.DDEEE0D4-ON80257689.003897F7-80257689.00398473@uk.ibm.com" type="cite">
Change the wording of 60011 from:

For an SCA reference with a JMS binding and a bidirectional interface, when a request message is sent >> as part of a request/response MEP << the SCA runtime MUST set the destination to which callback messages are to be sent as the value of the scaCallbackDestination user property in the message it creates [BJM60011].

to:

For an SCA reference with a JMS binding and a bidirectional interface, when a request message is sent as part of a request/response MEP the SCA runtime MUST set the scaCallbackDestination user property in the message it creates to a JMS URI string, in the format defined by the IETF URI Scheme for Java™ Message Service 1.0 [IETFJMS], that identifies the destination to which callback messages are to be sent [BJM60011].

-------------------------------------------------

Simon Holdsworth
STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair, AT&T and Boeing Lab Advocate
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