tag:blogger.com,1999:blog-6003063374827736283.post9026204211055994854..comments2010-08-14T01:01:57.611-07:00Paul Fremantlehttp://www.blogger.com/profile/15326219720808613358noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6003063374827736283.post-4467858235168656022008-04-02T09:18:00.000-07:002008-04-02T09:18:00.000-07:00Hi Paul & Sean,<BR/><BR/>I've been reading through the post and the comments since I am looking to implement a similar EDA pattern using an open source ESB.<BR/><BR/>I have figured out the way to do so in ServiceMix, using the JMS Binding Components that it offers to publish the consumers' requests to a queue, to which the providers will be subscribed to.<BR/><BR/>However, this implies crossing the JBI domain (the boundaries of the JBI containers), which doesn't seem an sufficiently attractive solution.<BR/><BR/>Plus, defining the equivalent of in-out sequences in ServiceMix is a real headache! (The best solution I've found is to use the Pipeline EIP or Static Routing Slip pattern). <BR/><BR/>Thus, I am really researching on the suitability of WSO2 for this scenario. So far, I've loved WSO2's sequence designer, it makes life so much easier!<BR/><BR/>Therefore, I would like to get at much information on how to use WSO2 for EDA... I am reading Sean's questions and they coincide with me, so I was wondering if you could send me the private reply you must have sent to Sean...<BR/><BR/>My email address: raul [dot] kripalani [at] atosorigin [dot] com.<BR/><BR/>Thanks a lot!Raulhttp://www.blogger.com/profile/08706241704323234260noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-81199193040997857442008-01-25T03:16:00.000-08:002008-01-25T03:16:00.000-08:00Paul,<BR/> Thanks for the reply. Sorry for the delay in getting back - work pressures. In essence what I want to do is an ED-SOA where my requests and replies from the WS clients and Web Services are asynchronous events (pure EDA).<BR/>My previous implementation of a WS was on Axis 1.2. All my messages had Http headers. If I use Axis2 (bundled with Synapse I believe) will I be able to send out my WS requests in an asynchronous fashion? Can Http be used asynchronously? If I use HTTP does that mean I need to use WS-Addressing for the reply? How will Esper fire and invoke the Web Service if there are http headers (how does Synapse decide when to strip the http headers from msgs and then pass to Esper?). <BR/>Can I use pub-sub? Tom Bernhardt felt JMS would be better suited to EDA as it supports pub-sub. What implications does that have?<BR/><BR/>As you can see I am trying to get my head around the detailed path to/from client/ws and where Synapse/Esper/Axis all fit in.<BR/><BR/>My email is skennedy@ait.ie if you would prefer not to use the blog.<BR/><BR/>Sorry for all the q's. Appreciate the help.<BR/><BR/>Sean.Sean Kennedyhttp://www.blogger.com/profile/12543126670522696470noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-38416394303250778042007-08-18T00:36:00.000-07:002007-08-18T00:36:00.000-07:00Sean<BR/><BR/>Synapse handles the HTTP headers and also the SOAP Enveloping. There is basically a utility method getXMLPayload, which returns the XML body of the message, which can then be handed to Esper. <BR/><BR/>You could do all this as HTTP request response, or you could do a combination of HTTP and JMS. For example the initial stream could be HTTP or SOAP, and the events that Esper generates could be sent to a JMS Topic. Alternatively you could have Synapse and Esper transparently "sniffing" an existing WS interaction and then sending new HTTP messages when it creates a new event.<BR/><BR/>Finally, Synapse supports both SOAP and pure XML/HTTP so you could do the RESTful approach as well.Paulhttp://www.blogger.com/profile/04602015245105431809noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-13761657269061019172007-08-17T07:43:00.000-07:002007-08-17T07:43:00.000-07:00Hi Paul,<BR/> I am trying to get an ED-SOA (Web Services) architecture implemented as part of my PhD. When I looked at a WS request on the wire, it had HTTP headers before the SOAP envelope - this caused Esper a problem (as it was not a valid XML document). Are these HTTP headers not present when the msgs are flowing through Synapse? (hence Esper will detect them). <BR/>The architecture I am thinking of is Service A on Machine A posts an event onto the ESB (Synapse) i.e. this is a Web service request. Service B on Machine B detects the event, fires and posts its response back into Synapse from where Machine A detects it. It appears to me that a pub/sub (JMS) would be the best protocol to use? Does this sound possible? If I used a HTTP request/reply model, would that work? I believe HTTP has issues with NATing... Also, I would be interested in implementing both RESTful and SOAP web services?<BR/><BR/>Thanks,<BR/>Sean.Sean Kennedyhttp://www.blogger.com/profile/12543126670522696470noreply@blogger.com