You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by "Micael Ericsson (QIN)" <Mi...@ein.ericsson.se> on 2001/08/27 12:15:11 UTC

RE: cannot create bean of class org.apache.soap.server.ServiceMan ager

We are running Tomcat 3.2.3 with Soap 2.2, and everything is running without problems. We upgraded 2 weeks ago from Tomcat 3.2.1 and Soap 2.1, which also was running without problems. 
We are using Solaris 7 as OS.

/Micael E.

-----Original Message-----
From: Tibeau Jacques [mailto:j_tibeau@hotmail.com]
Sent: Monday, August 27, 2001 12:04 PM
To: soap-user@xml.apache.org
Subject: Re: cannot create bean of class
org.apache.soap.server.ServiceManager


Hi

It worked when I upgraded tomcat to the version 3.2.3.
Is this faq? Or more likely I screwed up with tomcat 3.2.1
configuration?

Is there anybody that use SOAP 2.2 with tomcat 3.2.1 and 
have no problem?

TIA,

j

----- Original Message ----- 
From: Tibeau Jacques <j_...@hotmail.com>
To: <so...@xml.apache.org>
Sent: Sunday, August 26, 2001 2:46 PM
Subject: cannot create bean of class org.apache.soap.server.ServiceManager


> Hi 
> 
> I'm having a problem to get SOAP administration functins (list, deploy,
> un-deploy) working.
> 
> Here are my environment:
> Windows 2000 
> JDK 1.3
> Tomcat 3.2.1
> SOAP 2.2
> Xerces 1.3.1
> JavaMail 1.2
> JavaBeans Activation Framework 1.0.1
> Bean Scripting Framework 2.2
> 
> Whenever I try to deploy / list my web services, it returns 
> "Internal Servlet Error" as follows.
> 
> javax.servlet.ServletException:  Cannot create bean of class org.apache.soap.server.ServiceManager
> at admin._0002fadmin_0002fdeploy_0002ejspdeploy_jsp_2._jspService(_0002fadmin_0002fdeploy_0002ejspdeploy_jsp_2.java:83)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:177)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404)
> at org.apache.tomcat.core.Handler.service(Handler.java:286)
> at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
> at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
> at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
> at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210)
> at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
> at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
> at java.lang.Thread.run(Thread.java:484)
> 
> I confirmed this combination works fine with SOAP 2.0.
> So I guess there is somebody in this environment that 
> should be replaced with another version. Has anyone
> experienced similar problem?
> 
> TIA,
> 
> j
> 
> 
> 
> 
> 
> 
>