Hi Asanka - Thanks for the prompt clarifications.
Regarding Tomcat, when I start the WSO2-ESB it starts an embedded Tomcat server. I assumed the Synapse did so too and runs as a servlet in Tomcat and relied on Tomcat container for features such as clustering. Please correct me if I am wrong here. Yes we do like the fact Synapse uses NIO out of the box. Thanks Raj -----Original Message----- From: Asankha Perera [mailto:[email protected]] On Behalf Of Asankha C. Perera Sent: Wednesday, January 21, 2009 6:56 PM To: [email protected] Subject: Re: Synapse Axis2 Dependency Hi Raj > 1. Can the Web Service stack that hosts the actual service for > which Synapse esb provides Service delivery management/ Mediation be non > Axis2 (CXF or something else). Yes, definitely! It can be CXF, .Net, PHP.. etc > Do people normally use Axis2 on the back > when they use Synapse (meaning there is safety in using Axis2 on back > end though other stacks are possible). > Yes, and no.. some even use Synapse to mediate between SOAP / Hessian / JMS / POX etc.. > 2. If the backend is not Axis2, would I still be able to use > features such as WS-ReliableMessaging, WS-Security and WS-Addressing as > demonstrated in the example provided the backend service end point > supports these standards. Yes > Any gotchas? > This would be if the different implementations implement the standards slightly differently - which though not common is sometimes there.. next is if the implementations have bugs in them.. > 3. Can the Web Service Client that consumes Synapse ESB be based > on non-Axis2 based Yes, definitely! > or is there some interoperability issues that require > use of Axis2 client/ generation etc. For example the Axis2 > ServiceClient.fireAndForget() API use for one way messaging. > Not any I am aware of.. > 4. Has anyone tried running Synapse on anything other than Tomcat > container (just curious). > Many run Synapse standalone most of the time.. There is no added benefit on running it as a WAR on a JEE servlet container, as we use our own high performance non-blocking http/s transports > 5. Any info on constraints and limitations because of reliance on > Apache Rampart for Web Services security, Nothing I am aware of.. > Apache Kandula2 for WS transactions (I am not sure there any examples on this) No we do not rely on this, or have tested against this > & Apache Sandesha2 for WS Reliable messaging implementation etc. > There have been a few issues with RM in the past.. so its good to test it, especially with persistence etc > So far from what I have seen Synapse looks great. > Good to hear! and hope it will be useful to you cheers asankha -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com
