Re: ISSUE 18 - Clarify the rules on which queues and topics are used forresponses and callbacks

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

Here's the proposal for issue BINDINGS-18
http://www.osoa.org/jira/browse/BINDINGS-18

Solution proposal: 
Messages sent from a JMS reference with
a response queue have the JMS replyTo queue set to the response queue name.
For messages received by a service, by default the replyTo, if present,
overrides any defined response element. If scaCallbackQueue is present
in a message, the callback binding destination is ignored. Clarify that
in the callback/conversation section that the use of replyTo and service
callback queue are there for interacting with non-SCA applications 

Specific updates, referencing sca-jmsbinding-1.1-spec-WD-01.pdf:

Section 4, JMS Binding Schema, line
175/176, replace with the following text:

/binding.jms/response – defines the
resources used for handling response messages. References use this element
to define the resources used to receive responses, in which case the replyTo
destination in messages sent from such a reference should be set to the
identified destination.  Services use this element to define the resources
used to send responses.  In this case the replyTo destination in messages
received by such a service, if present, should be used in preference to
the destination element.

Section 7.2, line 282-291, replace with
the following text:

When an SCA component with a reference
with a bidirectional interface and JMS binding ("the sender")
invokes an operation on that interface, the JMS message that is sent may
identify the target for callbacks using the "scaCallbackQueue"
user property, or for one way operations the JMS replyTo header may be
used, to allow a level of interoperation with non-SCA JMS applications.

The invoked SCA component ("the
receiver") can only invoke operations on the callback interface during
the execution of the target operation for such a message, or when the service's
callback binding identifies a fixed callback queue. If the received message
includes a value for the scaCallbackQueue, then that should be used in
preference to any that may be defined on the service's callback binding.
Note that the use of a fixed callback queue is primarily for interaction
with non-SCA JMS applications, as SCA JMS applications should set the scaCallbackQueue
JMS user property. 

The sender's callback queue can be specified
on the reference's JMS callback binding, or it can be left to the runtime
to provide one, by omitting the callbackService element, the JMS callback
binding, or omitting the uri and destination from the JMS callback binding.




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

---

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