One difference is that I’m assuming
that we want to avoid introducing new SOAP headers into the WS-* world (let me
know if you disagree). The approach that we’ve adopted for JMS
includes the introduction of a new “scaCallbackQueue” header (which
is called a user property in JMS). If we want to avoid creating a new
SOAP header, then I think we need to figure out how to use headers that have
already been defined in some WS-* standard and use it in a way that is in
keeping with the standard.
From: Eric Johnson
Sent: Friday, February 22, 2008
To: Michael Rowley
Cc: OASIS Bindings; Anish
Karmarkar; Jim Marino
Subject: Re: [sca-bindings]
ISSUE-22: Callbacks for binding.ws
Am I missing something
Suppose for a moment that you ignore that "anonymous" reply channel
in HTTP, and every message uses WS-Addressing for a response (although
potentially it uses the "anonymous" channel).
How is this problem of callbacks over WS binding different from the four (five?
six?) week effort on JMS that we (but mostly Simon H.) went through trying to
figure out how to handle the JMSReplyTo header, depending on MEP, and
callbacks? With JMS there is a clear upside to using the JMSReplyTo
header, in that it is already a "Destination", thus overcoming some
If this is the same problem, does it deserve a solution that follows the same
pattern? Or, is it a characteristically different problem (as I think it
is), in that there isn't any "blessed" "reply" header that
is any more special than any other.
Michael Rowley wrote:
I’d like to get
this topic started. I’ve narrowed the subject line from the
original Issue 22 title, since I’d like this particular thread to be on
how callbacks could be handled in the WS-* world. We can handle
conversations and other bindings on other threads.
First, I’ll assume
that we will try to use WS-Addressing, if possible.
My first thought is that
it would be preferable to be able to leverage the ws-ReplyTo field, since I
believe that it should be possible to distinguish replies from callbacks, and I
also believe that callbacks should go to the same place that replies would go
to. I have a vague recollection that Anish preferred the use of
<wsa:from> rather than <wsa:replyTo> for passing callback ID
information. Unfortunately, I can’t find an email to that effect,
so I’ll ask that he confirm or deny that.
I've been thinking that
the client that is going to receive callbacks might want the reference
parameters that would be available if the service provider follows the rules
from the "Formulating a Reply Message" section of the WS-addressing
One way that a callback
could be distinguished from a reply is that the callback could have a
<relatesTo> header that uses a relationship type of
"oasis.org/isCallbackFor" and a reference to the messageID that the
callback is in response to. I haven’t seen other uses of the
<relatesTo> header, but it seems like this is exactly the sort of thing
it is meant for.
From: Eric Johnson [mailto:firstname.lastname@example.org]
Sent: Monday, February 04, 2008
To: Mike Edwards
Cc: OASIS Bindings
Subject: Re: [sca-bindings] ISSUE-22:
The Bindings specifications should provide exemplary Implementations for a)
Callbacks and b) Conversations
Logged as http://www.osoa.org/jira/browse/BINDINGS-22
Mike Edwards wrote:
Web Services Binding
specification, JMS Binding Specification, JCA Binding Specification
present, it is not clear which, if any, of the Bindings specifications enable the
implementation of two important
of SCA described in the Assembly specification - namely Callback interfaces and
of the Bindings specifications should explicitly declare if it is possible to
support each of these features.
each of the Bindings specifications that claim to support either or both of
these features, the specification
provide a full description of at least one exemplary implementation of the
feature using the Binding
described in the specification. Multiple alternative implementations are
permitted and may be
to the specification.
example, it may be possible to implement Callbacks using WS-Addressing
capabilities with Web services.
and example, showing the use of appropriate features of WS-Addressing and other
should be added to the specification. If an alternative exists using
(say) WS-Context, then an
based on that technology can also be provided.
Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile:
IBM United Kingdom Limited - Registered in England and Wales
with number 741598.
Registered office: PO Box 41, North
Harbour, Portsmouth, Hampshire
To unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php