Matt
Firstly, I do not like the idea of composing MakeConnection with
RM1.0. As you can see I've raised a JIRA about that. In addition, we
have now implemented the replay model for synchronous 2-way
interactions with WSRM1.0.
I think we need to make it easy to switch offer on and off, but I
think "out-of-the-box" interop on WSRM1.0 should be an objective, and
at the moment we don't have that.
Paul
On 3/21/07, Matt Lovett (JIRA) <[EMAIL PROTECTED]> wrote:
[
https://issues.apache.org/jira/browse/SANDESHA2-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482707
]
Matt Lovett commented on SANDESHA2-75:
--------------------------------------
This is actually quite a tricky issue. There are plenty of times that an offer
is inappropriate - suppose I want to set a reply-to to some third party, etc.
However, I agree that we want to interop with some other vendors that expect a
fairly rigid setup, and require an offer.
The case that really needs an offer is when doing sync 2-way without
MakeConnection. Unfortunately, the first call to a particular service might be
a 1-way, and the second call could be a 2-way, so as Paul already noted we need
to look at all of the operations on the service rather than the first operation
that we invoke.
For all aysnc cases, and for cases where we enable MakeConnection, I don't
think we _require_ an Offer, so leaving it as an optimization that the
programmer can enable seems appropriate.
Can we try to come to a consensus on list? I think it's worth having a proper
debate about this, as we are probably setting a precedent that will last for a
while. My view is that the WSRM spec level is not particularly relevant (after
all, you can compose MakeConnection with WSRM 1.0 if you choose).
Thanks, Matt
> Auto-Offer on two-way interactions
> ----------------------------------
>
> Key: SANDESHA2-75
> URL: https://issues.apache.org/jira/browse/SANDESHA2-75
> Project: Sandesha2
> Issue Type: Improvement
> Environment: Axis2 talking to other WSRM endpoints
> Reporter: Paul Fremantle
>
> Most WSRM endpoints "expect" an offer if the service they are offering has
any in-out operations. We don't make those offers unless the user codes them, meaning that
we don't interop as easily as we should. We ought to make an offer if there are any in-out
operations on the service.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
