This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have a project with Spring project which have a couple of Axis2 webservices. The porject gets deployed perfectly in Tomcat 6.0 and Glassfish.
However, when I try to deploy it in JBOSS 5.0, I run into problems with respect to the services. I can see from the server logs that the project is getting deployed and when I try to access the project using http://localhost:8080/<proj_name> I can see the Axis2 Home Page coming up as expected. However, when I try to access the services by clicking on the services link - nothing happens and after a while the request timeout. The server logs do not show any request coming in. It is the same case when I try to access the WSDL directly as well.
Please let me know if anyone have faced the same problem and have a solution.
Hi Aravind. I had the same problem just a minute ago. The services link did not work ... in my case, I deployed a simple Axis2 1.4.1 web service to tomcat (not JBoss). No idea why - (the Services link did work for me with Axis 1.5.1 though.)
I was not able to see the WSDL either when I tried to access the link directly - the result was the same, no response. I finally reinstalled my JBOSS instance and was able to access all the links.
I am not sure, however, I think the problem was with the servlet api jar that was present at the JBOSS instance at the point in time. I am not sure if I had played around with it and when my problem was fixed I tried to recreate it and noticed that when I went to a older/newer version of the servlet api jar - things stopped working.
Let me know if you have observed anything similar to this! Would appreciate any pointers to find out why the problem was present in the first place and if my recreation scenario was right!
Joined: Feb 19, 2010
Hi Aravind. Yes, if the correct servlet_api.jar is not present, then all bets are off. That has been my experience too.