I engaged synapse module to <span>SimpleStockQuoteService with a simple Synapse configuration with logging. When the client calls it gets the response as usual. But the Synapse log is not displayed as though Synapse never exists.
<br><br>Upul<br></span><br><div><span class="gmail_quote">On 8/30/07, <b class="gmail_sendername">Sanjiva Weerawarana</b> <<a href="mailto:sanjiva@wso2.com">sanjiva@wso2.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Did you try to engage Synapse against an Axis2 service and see whether you<br>could mediate the messages? That's the key thing we need to be able to do!<br><br>Sanjiva.<br><br>Upul Godage wrote:<br>> Hi,<br>><br>
> I was able to run Synapse SNAPSHOT on Axis2 1.3 WAR on top of Tomcat 5<br>> Servlet container. I have run some Synapse samples. Axis2 Version web<br>> service ran without any problems with Synapse deployed.<br>
><br>> What I did was,<br>> Deployed Axis2 1.3 WAR in Tomcat 5.<br>> In the exploded WAR,<br>> - added Synapse mar module.<br>> - module entry in axis2.xml<br>> - 4 Synapse jars + 2 Sandesha jars in axis2 WAR lib directory
<br>> - Synapse configuration xml given as a system variable (-D...) synapse.xml<br>> - Synapse home directory given as a system variable (-D...) for file<br>> locations when some samples needed files. e.g. WSDL file for proxy service
<br>><br>> Upul<br>><br>> On 8/30/07, *Upul Godage* <<a href="mailto:upulg.dev@gmail.com">upulg.dev@gmail.com</a><br>> <mailto:<a href="mailto:upulg.dev@gmail.com">upulg.dev@gmail.com</a>>> wrote:
<br>><br>> Hi,<br>><br>> I was able to run Synapse SNAPSHOT on Axis2 1.3 WAR on top of Tomcat<br>> 5 Servlet container. I have run some Synapse samples. Axis2 Version<br>> web service ran without any problems with Synapse deployed.
<br>><br>> What I did was,<br>> Deployed Axis2 1.3 WAR in Tomcat 5.<br>> In the exploded WAR,<br>> - added Synapse mar module.<br>> - module entry in axis2.xml<br>> - 4 Synapse jars + 2 Sandesha jars in axis2 WAR lib directory
<br>> - Synapse configuration xml given as a system variable (-D...)<br>> synapse.xml<br>> - Synapse home directory given as a system variable (-D...) for file<br>> locations when some samples needed files.
e.g. WSDL file for proxy<br>> service<br>><br>> Upul<br>><br>><br>><br>><br>><br>> On 8/30/07, *Asankha C. Perera* <<a href="mailto:asankha@wso2.com">asankha@wso2.com</a><br>> <mailto:
<a href="mailto:asankha@wso2.com">asankha@wso2.com</a>>> wrote:<br>><br>> Sanjiva<br>> > what I'm saying is that it should be possible for someone<br>> to use<br>
> > Synapse/ESB as a regular old Axis2 module without anything<br>> extra! The<br>> > limitations you mention are part of Axis2 (and any other<br>> WS-* runtime
<br>> > that uses regular servlets) too - and its something users<br>> are willing<br>> > to live with obviously (for some scenarios at least).<br>> Upul looked into this today, but so far the response from
<br>> Synapse did<br>> not reach the actual client that sent the request to<br>> Synapse. This<br>> requires a bit of debugging to find out the root cause.. I<br>
> will update<br>> on this as soon as we know something.<br>> > I still don't understand why you're opposed to just making<br>> it work<br>> > right as a "regular" Axis2 module and simply document all the
<br>> > limitations it comes with!<br>> No.. I am not opposed.. but I think the non-servlet model is<br>> better<br>> suited.. maybe I am wrong. We will certainly support both
<br>> options anyway<br>> for 1.1 release, and as soon as Upul figures out what needs<br>> to be done<br>> we could discuss specifics<br>> > Oh BTW have you guys made progress with moving the NIO
<br>> transport to<br>> > Axis2? Axis2 needs that too for sure.<br>> Yep.. this went into the Axis2 1.3 release<br>><br>> thanks<br>> asankha
<br>><br>> _______________________________________________<br>> Esb-java-dev mailing list<br>> <a href="mailto:Esb-java-dev@wso2.org">Esb-java-dev@wso2.org</a> <mailto:<a href="mailto:Esb-java-dev@wso2.org">
Esb-java-dev@wso2.org</a>><br>> <a href="http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev">http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev</a><br>> <<a href="http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev">
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev</a>><br>><br>><br>><br>><br>><br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________
<br>> Esb-java-dev mailing list<br>> <a href="mailto:Esb-java-dev@wso2.org">Esb-java-dev@wso2.org</a><br>> <a href="http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev">http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
</a><br><br>--<br>Sanjiva Weerawarana, Ph.D.<br>Founder, Chairman & CEO; WSO2, Inc.; <a href="http://www.wso2.com/">http://www.wso2.com/</a><br>email: <a href="mailto:sanjiva@wso2.com">sanjiva@wso2.com</a>; cell: +94 77 787 6880; fax: +1 509 691 2000
<br><br>"Oxygenating the Web Service Platform."<br><br>_______________________________________________<br>Esb-java-dev mailing list<br><a href="mailto:Esb-java-dev@wso2.org">Esb-java-dev@wso2.org</a><br><a href="http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev">
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev</a><br></blockquote></div><br>