Hi -
I downloaded and worked thru the examples that ship with the Synapse. I understand the packaged examples make use of Axi2 Server to host the StockQuote service and use Axis2 clients to invoke the Proxy service exposed via the Synapse ESB. However I would appreciate if someone could explicitly make it clear if there are any dependencies between Synapse as ESB and the actual web services stack on the client side and Service backend. For example: 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). 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). 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. Any gotchas? 3. Can the Web Service Client that consumes Synapse ESB be based on non-Axis2 based 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. 4. Has anyone tried running Synapse on anything other than Tomcat container (just curious). 5. Any info on constraints and limitations because of reliance on Apache Rampart for Web Services security, Apache Kandula2 for WS transactions (I am not sure there any examples on this) & Apache Sandesha2 for WS Reliable messaging implementation etc. So far from what I have seen Synapse looks great. Thanks for your help. Raj
