I see an entry by Deepal indicating that the bug is resolved in the following revision. Maybe the patch that was supplied was not added as-is but was refactored? There seems to be a lot of changes to the file in that revision.
Revision: 498980 Author: deepal Date: 2:42:35 AM, Tuesday, January 23, 2007 Message: fixing AXIS2-1488 ---- Modified /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/transport/http/AxisServlet.java Shantanu ----- Original Message ---- From: Asankha C. Perera <[EMAIL PROTECTED]> To: [email protected] Cc: Deepal Jayasinghe <[EMAIL PROTECTED]> Sent: Tuesday, March 20, 2007 2:27:18 PM Subject: Re: Axis2 SOAP-over-JMS Deepal Could you answer this question? thanks asankha Shantanu Sen wrote: I pulled the source code from the trunk, but still do not see the patch in the AxisServlet i.e. the initializeAllTransportReceiversButHttp that was added in the AxisServlet as specified in https://issues.apache.org/jira/browse/AXIS2-1488 cannot be found. Does that mean that the patch is yet to be checked in? If the patch is checked in, which branch is it checked in at? I thought that the head branch should contain it. Thanks, Shantanu Sen ----- Original Message ---- From: Asankha C. Perera <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, March 20, 2007 2:01:39 AM Subject: Re: Axis2 SOAP-over-JMS Hi Badrys First thank you for answering. I almost became hopeless :) There is always hope and support :-)! Concerning your question : yes I'm using Axis2 on Tomcat and for JMS I'm using Apache ActiveMQ, but I don't know how to check wether the JMS transport start or not. Actually I'm quite sure it doesn't since there isn't any reference to a "JMS port" in the generated wsdl file. As I guessed.. thats why I made it my first question.. there is a defect for this https://issues.apache.org/jira/browse/AXIS2-1488 which is marked fixed, but doesn't specify the version.. so I would expect that the issue is still out there.. and if you cannot change your code (i.e. recompile) or use the standalone dist I cannot offer you another solution right now :-( asankha I think the problem is due to the "axis2.xml" configuration: I just uncommented the part dealing with JMS and I didn't modify any attribute or any value since it already uses ActiveMQ as example. Plus I'm not sure I put the right attributes concerning JMS in my "services.xml". Have you already dealt with those xml files ? Thanks again for helping me. asankha wrote: Hi Are you using Axis2 on Tomcat? Do you see the JMS transport starting? asankha badrys wrote: Hello ! Has anybody succeded to run a simple SOAP-over-JMS web service sample such as the "echo" one mentioned in the Apache documentation ?(http://ws.apache.org/axis2/1_1/jms-transport.html). I followed the all the instructions given in the documentation (axis2.xml and service.xml modifications) but Axis2 seems to be generating a wrong wsdl file since there is no reference to JMS in it and the wsdl2java tool can't recongnize it as a valid wsdl. Here are the web service archive and the generated wsdl. Can you help me with that ? thanks in advance. P.S. the sample works perfectly with "http" (instead of JMS) which is the default transport used by Axis. http://www.nabble.com/file/7265/Echo2.aar Echo2.aar http://www.nabble.com/file/7266/echo2.wsdl echo2.wsdl --------------------------------------------------------------------- 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]
