The mode that Synapse currently does support for WS-Reliable Messaging is by letting Synapse deal with the RM communication with the target endpoint service. By using this scenario the client does not have to implement any WS-RM related functionality, Synapse will handle this. You can use the following Synapse configuration for this:
<synapse xmlns="http://ws.apache.org/ns/synapse"> <rules> <log level="full"/> <RMSequence ( correlation="xpath" [last-message="xpath"] ) | single="true" [version="1.0|1.1"/> <send> <endpoint address="http://localhost:8081/axis2/services/RMSampleService" /> </send> </rules> </synapse> If you use want to send 1 message in a sequence to the endpoint you can simply use the following RMSequence configuration: <RMSequence single="true" version="1.1"/> Hope this provides an alternative solution. Tijs ---- Paul Fremantle <[EMAIL PROTECTED]> schreef: > 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 <[EMAIL PROTECTED]> wrote: > > On 3/8/07, Lorenzo <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > 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 > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
