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

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

Mike,

What makes the binding a JMS binding
is primarily the reliance on the JMS standard entities that are destinations,
connection factories and activation specs to describe the manner in which
the binding accesses the underlying messaging transport, and the JMS message
headers that provide a means to specify some delivery options.  The
JMS URI just defines a way to resolve a particular JMS destination and
set some delivery options, so I don't see that requiring the URI to be
a JMS URI as defined by IETF is really restricting anything as far as the
JMS binding is concerned.  If we want to generalise the URI then that
would be an argument for generalizing the binding as a whole - why allow
reference to messaging resources that are not defined using JMS entities
in the URI, if you can't do that using the JMS binding elements?

Regards, Simon

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

From:	Mike Edwards/UK/IBM@IBMGB
To:	sca-bindings@lists.oasis-open.org
Date:	17/12/2009 11:30
Subject:	Re: [sca-bindings] Updated proposal for BINDINGS-94

---

Folks, 

I have some sympathy with Eric's point.  However, I suppose the alternative
argument can be made that IF the 
binding is a JMS binding, then it must support the JMS URI.

However, a JMS binding really says very little about the underlying transport,
so perhaps something more 
permissive is wise here. 


Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
Email:  mike_edwards@uk.ibm.com

From:	Eric Johnson <eric@tibco.com>
To:	sca-bindings@lists.oasis-open.org
Date:	17/12/2009 02:58
Subject:	Re: [sca-bindings] Updated proposal for BINDINGS-94

---

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

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

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?


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.


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

---

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

---

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