Asankha, Are you saying that the proxy service with RM for the backend service should already be working? If this is so, can you maybe provide me with an example of the Synapse Configuration Language for this? Let me explain the background for my question. I am working on a Enterprise Integration Patterns (EIP) in Action book that will be published at Manning. We are implementing a selection of valuable EIP (of the Hohpe/Woolf book) in this book with messaging based integration with Mule and web services integration with Synapse. One of the patterns is guaranteed delivery, so I would like an implementation where a client sends a SOAP message to Synapse, and Synapse uses reliable messaging to call the backend service. Another question that I have is if there is an interest with some of the developers of the Synapse project to help with gathering the necessary information for implementing the EIPs? I think it would also be a valuable asset for the Synapse project if it could say that it supports many EIP.
Thanks, Tijs > > van: "Asankha C. Perera" <[EMAIL PROTECTED]> > datum: 2006/08/16 Wed AM 07:33:43 CEST > aan: [email protected] > onderwerp: Re: Reliable Messaging > > Tijs > > Have you tried creating a proxy service with RM for your backend service > instead? The RM mediator is a complex case to implement, as Synapse has > to process a message through the RM module after we have accepted it - > so I guess it will take a few days for us to complete it. So if proxy > services model works for you, it will be easier to use and ready. > > asankha > > [EMAIL PROTECTED] wrote: > > Asankha, > > > > Thanks for the reply. > > It would be great if Saminda could get back to me on this. > > To me it also seems that the RM mediator is not 100% working yet. > > In the last post I states that it was working with Synapse just as a proxy, > > but that is not right. > > It only works when my client web service is directly communicating with the > > target web service with Reliable Messaging. > > With Synapse it is just not working. > > > > Thanks, > > > > Tijs > > > > > > Tijs > > > > Sorry for the delay in responding, as some of the members are attending the > > ApacheCon Asia this week. As far as I know the RM mediator is not 100% > > completed yet.. let me get Saminda to reply to your email tomorrow, as he > > was implementing the RM mediator. > > > > asankha > > > > [EMAIL PROTECTED] wrote: > > I hope somebody of the Synapse team can give an answer to question about > > ReliableMessaging. > > I have an example of reliable messaging implemented with a web service > > client that engages the sandesha2 > > module that sends the message to Synapse and Synapse then forwards the > > message to the target web service. > > But this only uses Synapse as a delegate mechanism. > > Can somebody tell what the functionality of the WS-Reliability support in > > Synapse is? > > Is it just delelgation support or is it an implementation that makes it > > possible to have a client that is unaware of RM and > > that Synapse taken care of the RM functionality? > > > > Thanks, > > > > Tijs > > > > van: <[EMAIL PROTECTED]> > > datum: 2006/08/13 Sun PM 11:00:29 MEST > > aan: <[email protected]> > > onderwerp: Reliable Messaging > > > > Hi there, > > > > I am trying to get the reliable messaging mediator of Synapse to work in my > > example, but I don't succeed. > > I am using the <enableRM/> mediator before I am using the send mediator. > > The message that is coming is send according to the Sandesha2 examples and > > is also working without Synapse. > > But I simply can not get it to work with using Synapse. Can anybody help me > > with an example of how set this up? > > > > Thanks, > > > > Tijs > > > > > > --------------------------------------------------------------------- > > 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] > > > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
