Axis2 in WSAD

[Viv Gupta]

Hi,
How can i configure Axis2 for WSAD 5.1.1 ? Installation guide on ws.apache.org says that it can be deployed by copying the war on webapps folder of any servlet container. Almost all servlet container accepts the axis that way.

So I created a axis2.war and imported that war on WSAD. But the server throwing exception while starting up.

    
 Did not realize  init() exception thrown by servlet AxisServlet: javax.servlet.ServletException
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:195)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doInit(StrictServletInstance.java:82)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._init(StrictLifecycleServlet.java:147)
at com.ibm.ws.webcontainer.servlet.PreInitializedServletState.init(StrictLifecycleServlet.java:270)
.
.
.
.
[5/22/06 17:00:48:146 IST] 3ded4bbe WebGroup      E SRVE0020E: [Servlet Error]-[AxisServlet]: Failed to load servlet: java.lang.NullPointerException
at org.apache.axis2.deployment.WarBasedAxisConfigurator.<init>(WarBasedAxisConfigurator.java:81)
at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:213)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:182)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doInit(StrictServletInstance.java:82)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._init(StrictLifecycleServlet.java:147)
at com.ibm.ws.webcontainer.servlet.PreInitializedServletState.init(StrictLifecycleServlet.java:270)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.init(StrictLifecycleServlet.java:113)
at com.ibm.ws.webcontainer.servlet.ServletInstance.init(ServletInstance.java:189)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.addServlet(WebAppServletManager.java:870)
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:224)

Can any body point out where Iam wrong.

[Tim Manchester]

Please read my earlier article on the subject here.

Regards,

Tim Manchester
[ May 23, 2006: Message edited by: Tim Manchester ]