I have been able to verify that the contrib/tomcat/tomcat-test.ear works with the 
current
cvs codebase using Jetty, but not the current EmbeddedTomcat release. When using
a clean build of both jboss and contrib/tomcat with some config tweaking I get the
beans to deploy fine, but invoking them via a servlet produces an error. Note that
the bean deployment msgs does not have the
'[Container factory] There are no interceptors configured. Check the standardjboss.xml 
file.
msg that Dewayne saw. At this point I don't see a generic problem with the
container-interceptors change. I'll follow up with Dewayne offline to see if we can
get tomcat working.


Deployment msgs:
[Auto deploy] Auto deploy of 
file:/D:/usr/local/src/cvsroot/jBoss/jboss/dist/deploy/tomcat-test.ear
[J2EE Deployer Default] Deploy J2EE application: 
file:/D:/usr/local/src/cvsroot/jBoss/jboss/dist/deploy/tomcat-test.ear
[J2EE Deployer Default] Create application tomcat-test.ear
[J2EE Deployer Default] inflate and install module tomcat-test.war
[J2EE Deployer Default] added 
jar:file:D:\usr\local\src\cvsroot\jBoss\jboss\dist\tmp\deploy\Default\copy1001.zip!/client.jar
 to
common classpath
[J2EE Deployer Default] install module tomcat-test.jar
[J2EE Deployer Default] add all ejb jar files to the common classpath
[J2EE Deployer Default] Starting module tomcat-test.war
2001-02-10 05:21:29 - ContextManager: Adding context Ctx( /jboss )
[J2EE Deployer Default] Starting module tomcat-test.jar
[Container factory] 
Deploying:file:/D:/usr/local/src/cvsroot/jBoss/jboss/dist/tmp/deploy/Default/tomcat-test.ear/ejb1002.jar
[Verifier] Verifying 
file:/D:/usr/local/src/cvsroot/jBoss/jboss/dist/tmp/deploy/Default/tomcat-test.ear/ejb1002.jar
[Container factory] Deploying Optimized
[Container factory] Deploying NonOptimized
[Container factory] Deployed application:
file:/D:/usr/local/src/cvsroot/jBoss/jboss/dist/tmp/deploy/Default/tomcat-test.ear/ejb1002.jar
[J2EE Deployer Default] J2EE application: 
file:/D:/usr/local/src/cvsroot/jBoss/jboss/dist/deploy/tomcat-test.ear is deployed.

ServletException on loading http://localhost:8080/jboss/servlet/HelloEJB?speed:

Servlet calling EJB
Call failed... Exception:
javax.naming.CommunicationException.  Root exception is 
java.lang.ClassNotFoundException:
org.jboss.test.tomcat.ejb.interfaces.StatelessSessionHome
 at javax.management.loading.MLet.findClass(MLet.java:800)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:195)
 at sun.rmi.server.MarshalInputStream.resolveProxyClass(MarshalInputStream.java:183)
 at java.io.ObjectInputStream.inputProxyClassDescriptor(ObjectInputStream.java:982)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
 at java.rmi.MarshalledObject.get(MarshalledObject.java:138)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:299)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:279)
 at javax.naming.InitialContext.lookup(InitialContext.java:350)
 at org.jboss.test.tomcat.servlet.HelloEJB.testBean(HelloEJB.java:62)
 at org.jboss.test.tomcat.servlet.HelloEJB.doGet(HelloEJB.java:43)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 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 am using the jakarta-tomcat-3.2.1 binary release of tomcat.


----- Original Message -----
From: "marc fleury" <[EMAIL PROTECTED]>
To: "jBoss Developer" <[EMAIL PROTECTED]>
Sent: Saturday, February 10, 2001 10:53 AM
Subject: RE: [jBoss-Dev] Re: [jBoss-User] Apache+Tomcat+jBoss


> This has to do with the container externalization done recently... if the
> stuff finds jboss.xml but you don't specify the stacks then it dies ... We
> need to look in it.
>
> Does the container externalization work in case we specify a configuration?
> it seems not in a differential way (just specify the configuration you want
> like it was in tomcat's jboss.xml below
>
> marc
>
>
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of Dewayne McNair
> |Sent: Friday, February 09, 2001 8:57 PM
> |To: jBoss Developer
> |Subject: Re: [jBoss-Dev] Re: [jBoss-User] Apache+Tomcat+jBoss
> |
> |
> |Sorry to flood everyone, but, problem solved!
> |
> |I added a set of <container-interceptors> and
> |<persistence-manager></persistence-manager> to both of the
> |<container-configurations> and JBoss started picking them up.  The
> |tomcat-test.ear file now works perfectly.  I'm going to complete the docos
> |and commit the changes ASAP.
> |
> |----- Original Message -----
> |From: "Dewayne McNair" <[EMAIL PROTECTED]>
> |Sent: Friday, February 09, 2001 10:25 PM
> |Subject: Re: [jBoss-Dev] Re: [jBoss-User] Apache+Tomcat+jBoss
> |
> |
> |> I'm on to something... if I comment out the container lines in the
> |> jboss.xml, everything works.  So, it's something to do with the container
> |> information.  Below is the jboss.xml file from CVS.  If I comment out
> |> everything between <jboss> and </jboss> the servlet calls the EJB just
> |fine.
> |> Can anyone spot a problem?  For some reason, the new
> |> container-configurations are not being picked up.
> |>
> |> contrib/tomcat/src/resources/test/META-INF/jboss.xml
> |
> |<snip>
> |
> |
>
>
>


Reply via email to