Thank you very much or the tip!
Removing the servletapi-2.3.jar file from the WAR file seemed to do the trick.
The error that the AxisServlet is not a servlet is gone and I see the
AxisServlet and SOAPMonitorService initialized. I was able to run a successful
echo test.
I'm not sure I am home
Hi,
the reason for this error message is usually, that you included the
javax.servlet.Servlet class somewhere in a jar in your web-inf/lib
directory. Delete that jar and it should work.
If you have classloader problems regarding axis2, it may help to add the
jars by adding them as "shared li
I already had the application itself set to loading parent last. However, I
had not changed the WAR class loader policy option to "single class loader for
application."
Making that change got rid of the error, but now when I try to invoke my
service I get the following error:
Error 404: SRVE02
I'm running Axis2 with websphere 6.1 without any problem.
The issue you have seems to be the same as the one depicted here:
http://ws.apache.org/muse/docs/2.2.0/manual/troubleshooting/wsdl4j-version-on-websphere.html
Pierre
Jack Sprat <[EMAIL PROTECTED]>
31/07/2007 16:25
Veuillez répondre à
