Logged as: http://www.osoa.org/jira/browse/BINDINGS-18
-Eric.
Simon Holdsworth wrote:
OF42518E1A.B0CC80A1-ON8025739B.0052FF2A-8025739B.0053BAE0@uk.ibm.com"
type="cite">
Target: JMS binding
Description: The JMS binding spec currently doesn't say how the
response
and callback element definitions relate to messages that are sent from
a reference, and those sent by a service, and what the precedence of
the
message's replyTo and scaCallbackQueue are relative to the SCDL
definitions.
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
Possible additional updates that
relate
to these:
Add "overrideReplyTo={true|false}"
attribute to the <response> element for a service indicating
always
use vs. only use if no replyTo specified in a given received message -
false is the default).
Add
"overrideCallbackQueue="{true|false}"
attribute to <binding.jms>, which applies when the binding is
used
on a service callback, to indicate whether the service callback queue
is
always used or only when no replyTo and scaCallbackQueue in a received
request message.
Add "useForCallback="{true|false}"
attribute to the <response> element for a reference that
inficates
that callbacks should go to the replyTo queue without having to
duplicate
the definition in a callback service binding.
Simon Holdsworth
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
|