You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by Lorenzo <ce...@gmail.com> on 2007/03/08 14:57:38 UTC
Synapse in a ws-rm conversation
Hi all,
i'm making some experiments with Synapse and ws-rm.
i make the echo sample with WS-ReliableMessage and everyting goes fine
then i try to put synapse in the middle with this config:
<synapse xmlns="http://ws.apache.org/ns/synapse">
<rules>
<log level="full"/>
<send>
<endpoint
address="http://localhost:8081/axis2/services/RMSampleService" />
</send>
</rules>
</synapse>
but don't work.. so i put one tcpmonitor between client and synapse and
one between synapse and server and i notice this:
client send a CreateSequence to Synapse
synapse send a CreateSequence to Server
server send a CreateSequenceResponse to Synapse
synapse don't send nothing...
where I am mistaking?
Thx
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Re: Synapse in a ws-rm conversation
Posted by Ruwan Linton <ru...@gmail.com>.
Paul,
Yes I have missed that RM should be end-to-end, (end-to-end argument) so
that the messageflow should be createSequence from client to Synapse to
server and the createSequenceResponse from server to Synapse to client.
Have to look more in to this why this is not working....
Thanks for correcting me
Ruwan.
On 3/9/07, Paul Fremantle <pz...@gmail.com> wrote:
>
> Ruwan
>
> I think you've misunderstood the situation. One of the aims of WSRM is
> to provide end-to-end reliable messaging, independent of the
> intermediaries. So forget for a moment that we have RM support in
> Synapse and think of Synapse as an HTTP Proxy. In that case, Synapse
> should just be ignoring the RM headers and carrying on as normal. And
> for the RM messages like CreateSeq and CreateSeqResponse, RM should
> pass those through without touching them.
>
> Now we add RM support, which allows Synapse to do cool things like
> enabling RM when the target services don't support it. That's very
> cool, but if the user doesn't want that, we should just act as a proxy
> and pass the messages through without doing anything except the normal
> routing.
>
> Paul
>
> On 3/9/07, Ruwan Linton <ru...@gmail.com> wrote:
> > On 3/9/07, Paul Fremantle <pz...@gmail.com> wrote:
> > >
> > > Ruwan
> > >
> > > I agree the model you are proposing will work. However, what Lorenzo
> > > is trying should work out of the box. If we don't explicitly enable or
> > > disable RM then it should be flowed just the same as any other
> > > message.
> >
> >
> > Yes Paul,
> >
> > It should be the case but I think with the clue that Lorenzo has given
> >
> > > > client send a CreateSequence to Synapse
> > > > synapse send a CreateSequence to Server
> > > > server send a CreateSequenceResponse to Synapse
> > > > synapse don't send nothing...
> >
> > this should not be the message sequence if it is working.
> >
> > When client send a createSequence to Synapse, what Synapse should do is
> > sending the createSequenceResponse to client, but instead Synapse has
> sent
> > the createSequence to the Server which is incorrect. May be Sandesha
> module
> > is not engaged properly for Synapse. According to his observation we are
> not
> > handling the reliable messaging at Synapse and it just forward the
> > createSequence call to the server and server send the
> createSequenceResponse
> > to Synapse which will be neglected by Synapse.
> >
> > We need to look in to this, I think we have to do some extra work to
> handle
> > this scenario.
> >
> > Ruwan.
> >
> >
> > --
> > Ruwan Linton
> > http://www.wso2.org - "Oxygenating the Web Services Platform"
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Synapse in a ws-rm conversation
Posted by Paul Fremantle <pz...@gmail.com>.
Ruwan
I think you've misunderstood the situation. One of the aims of WSRM is
to provide end-to-end reliable messaging, independent of the
intermediaries. So forget for a moment that we have RM support in
Synapse and think of Synapse as an HTTP Proxy. In that case, Synapse
should just be ignoring the RM headers and carrying on as normal. And
for the RM messages like CreateSeq and CreateSeqResponse, RM should
pass those through without touching them.
Now we add RM support, which allows Synapse to do cool things like
enabling RM when the target services don't support it. That's very
cool, but if the user doesn't want that, we should just act as a proxy
and pass the messages through without doing anything except the normal
routing.
Paul
On 3/9/07, Ruwan Linton <ru...@gmail.com> wrote:
> On 3/9/07, Paul Fremantle <pz...@gmail.com> wrote:
> >
> > Ruwan
> >
> > I agree the model you are proposing will work. However, what Lorenzo
> > is trying should work out of the box. If we don't explicitly enable or
> > disable RM then it should be flowed just the same as any other
> > message.
>
>
> Yes Paul,
>
> It should be the case but I think with the clue that Lorenzo has given
>
> > > client send a CreateSequence to Synapse
> > > synapse send a CreateSequence to Server
> > > server send a CreateSequenceResponse to Synapse
> > > synapse don't send nothing...
>
> this should not be the message sequence if it is working.
>
> When client send a createSequence to Synapse, what Synapse should do is
> sending the createSequenceResponse to client, but instead Synapse has sent
> the createSequence to the Server which is incorrect. May be Sandesha module
> is not engaged properly for Synapse. According to his observation we are not
> handling the reliable messaging at Synapse and it just forward the
> createSequence call to the server and server send the createSequenceResponse
> to Synapse which will be neglected by Synapse.
>
> We need to look in to this, I think we have to do some extra work to handle
> this scenario.
>
> Ruwan.
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Re: Synapse in a ws-rm conversation
Posted by Ruwan Linton <ru...@gmail.com>.
On 3/9/07, Paul Fremantle <pz...@gmail.com> wrote:
>
> Ruwan
>
> I agree the model you are proposing will work. However, what Lorenzo
> is trying should work out of the box. If we don't explicitly enable or
> disable RM then it should be flowed just the same as any other
> message.
Yes Paul,
It should be the case but I think with the clue that Lorenzo has given
> > client send a CreateSequence to Synapse
> > synapse send a CreateSequence to Server
> > server send a CreateSequenceResponse to Synapse
> > synapse don't send nothing...
this should not be the message sequence if it is working.
When client send a createSequence to Synapse, what Synapse should do is
sending the createSequenceResponse to client, but instead Synapse has sent
the createSequence to the Server which is incorrect. May be Sandesha module
is not engaged properly for Synapse. According to his observation we are not
handling the reliable messaging at Synapse and it just forward the
createSequence call to the server and server send the createSequenceResponse
to Synapse which will be neglected by Synapse.
We need to look in to this, I think we have to do some extra work to handle
this scenario.
Ruwan.
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Synapse in a ws-rm conversation
Posted by Paul Fremantle <pz...@gmail.com>.
Ruwan
I agree the model you are proposing will work. However, what Lorenzo
is trying should work out of the box. If we don't explicitly enable or
disable RM then it should be flowed just the same as any other
message.
Paul
On 3/9/07, Ruwan Linton <ru...@gmail.com> wrote:
> On 3/8/07, Lorenzo <ce...@gmail.com> wrote:
> >
> > Hi all,
> >
> > i'm making some experiments with Synapse and ws-rm.
> > i make the echo sample with WS-ReliableMessage and everyting goes fine
> > then i try to put synapse in the middle with this config:
> >
> > <synapse xmlns="http://ws.apache.org/ns/synapse">
> > <rules>
> > <log level="full"/>
> > <send>
> > <endpoint
> > address="http://localhost:8081/axis2/services/RMSampleService" />
> > </send>
> > </rules>
> > </synapse>
> >
> > but don't work.. so i put one tcpmonitor between client and synapse and
> > one between synapse and server and i notice this:
> > client send a CreateSequence to Synapse
> > synapse send a CreateSequence to Server
> > server send a CreateSequenceResponse to Synapse
> > synapse don't send nothing...
> >
> > where I am mistaking?
>
>
> Currently Synapse does not support rm for message mediation. Instead of just
> message mediation you can create a proxy service in synapse enabling RM fro
> the proxy and specify the endpoint in the target enabling RM and you need to
> call the synapse proxy. So that synapse will handle RM with client and
> Service separately. If you follow this approach it should work, but
> definitely we need to do an improvement on your above scenario.
>
> Thx
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: synapse-user-help@ws.apache.org
> >
> >
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Re: Synapse in a ws-rm conversation
Posted by Ruwan Linton <ru...@gmail.com>.
On 3/8/07, Lorenzo <ce...@gmail.com> wrote:
>
> Hi all,
>
> i'm making some experiments with Synapse and ws-rm.
> i make the echo sample with WS-ReliableMessage and everyting goes fine
> then i try to put synapse in the middle with this config:
>
> <synapse xmlns="http://ws.apache.org/ns/synapse">
> <rules>
> <log level="full"/>
> <send>
> <endpoint
> address="http://localhost:8081/axis2/services/RMSampleService" />
> </send>
> </rules>
> </synapse>
>
> but don't work.. so i put one tcpmonitor between client and synapse and
> one between synapse and server and i notice this:
> client send a CreateSequence to Synapse
> synapse send a CreateSequence to Server
> server send a CreateSequenceResponse to Synapse
> synapse don't send nothing...
>
> where I am mistaking?
Currently Synapse does not support rm for message mediation. Instead of just
message mediation you can create a proxy service in synapse enabling RM fro
the proxy and specify the endpoint in the target enabling RM and you need to
call the synapse proxy. So that synapse will handle RM with client and
Service separately. If you follow this approach it should work, but
definitely we need to do an improvement on your above scenario.
Thx
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Synapse in a ws-rm conversation
Posted by Paul Fremantle <pz...@gmail.com>.
Seems like a bug! Can you please create a JIRA with the TCPMON flows
so we can debug?
Thanks
Paul
On 3/8/07, Lorenzo <ce...@gmail.com> wrote:
> Hi all,
>
> i'm making some experiments with Synapse and ws-rm.
> i make the echo sample with WS-ReliableMessage and everyting goes fine
> then i try to put synapse in the middle with this config:
>
> <synapse xmlns="http://ws.apache.org/ns/synapse">
> <rules>
> <log level="full"/>
> <send>
> <endpoint
> address="http://localhost:8081/axis2/services/RMSampleService" />
> </send>
> </rules>
> </synapse>
>
> but don't work.. so i put one tcpmonitor between client and synapse and
> one between synapse and server and i notice this:
> client send a CreateSequence to Synapse
> synapse send a CreateSequence to Server
> server send a CreateSequenceResponse to Synapse
> synapse don't send nothing...
>
> where I am mistaking?
>
>
> Thx
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org