NEW ISSUE: JMS callback specification does not cater for callbacks usingother bindings

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

TARGET:

JMS binding 

DESCRIPTION:

The current description of callback protocol for JMS has a JMS user property
called scaCallbackDestination.  The use of this property is described
in terms of carrying a JMS Destination name that is used for callbacks.
 In theory, a different binding can be used for callbacks, which means
that the scaCallbackDestination needs to be able to hold the endpoint address
for any binding that is being used for callbacks.

PROPOSAL:

The user property name scaCallbackDestination is sufficiently general that
it could reasonably hold information regarding non-JMS endpoints, although
we may want to consider renaming it to scaCallbackAddress to make the generality
more obvious.  We also need to clarify that JMSReplyTo can only be
used for callbacks when the callback binding is JMS.

The following lines show how text should be changed
to make this neutral; more lines need changing; I'll add details if the
issue is accepted.

329/330: "scaCallbackDestination"
holds the endpoint address which callback messages are sent. This endpoint
address is of an appropriate format for the callback binding. When the
callback binding is binding.jms, this is a JMS Destination name.

339-344: A callback
operation can be one-way or request/response.  Messages that correspond
to one-way or request/response operations on a bidirectional interface
use either the scaCallbackDestination user property or the
JMSReplyTo destination, or both, to identify the endpoint
address to which messages are to be sent when operations are invoked on
the callback interface.  The use of JMSReplyTo for this
purpose is to enable interaction with non-SCA JMS applications, as described
below, and can only be used when binding.jms is the callback binding.

346-348: When
a request message is sent by a reference with a JMS binding for a one-way
MEP with a bidirectional interface, the SCA runtime MUST set the endpoint
address to which callback messages are to be sent as the value of the scaCallbackDestination
user property in the message it creates.  

350-352: When
a request message is sent by a reference with a JMS binding for a request/response
MEP with a bidirectional interface, the SCA runtime MUST set the scaCallbackDestination
user property in the message it creates to identify the endpoint address
that is to be used to receive callback messages.

359-362: An
SCA service with a callback interface can invoke operations on that callback
interface by sending messages to the endpoint address identified by the
scaCallbackDestination user property in a message that it
has received, the JMSReplyTo destination of a one-way message
that it has received (when the service's callback binding is JMS), or the
endpoint address identified by the service's 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