Scott,
I saw that you were identified as the owner of the bug; if you
believe there is a straight forward solution and can point me in the
right direction I'd be happy to take a look at it and see what I can
come up with.
It seems like you would have to wait for the container to deploy
the EJB's and then signal Tomcat to execute the servlets identified
in the load on startup.
John Moore
-----Original Message-----
From: Scott M Stark [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 16, 2001 3:56 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Embedded Tomcat Load-On-Startup w/ EJB's
Embedded Tomcat Load-On-Startup w/ EJB'sIts a startup ordering bug that
needs to be fixed.
----- Original Message -----
From: John Moore
To: jBoss Users (E-mail)
Sent: Monday, May 14, 2001 11:54 AM
Subject: [JBoss-user] Embedded Tomcat Load-On-Startup w/ EJB's
We have a servlet that loads static data into the application object through
our entity beans; everything is running in jboss /w embedded tomcat.
Because Embedded Tomcat starts before the EJB container the servlet can't
get to the data. I moved embedded tomcat to the end of the load sequence
(jboss.jcml) and it worked but .ear's can't be deployed. Other than a
timer, is their a signal/listener that i can register with to wait for JBoss
to deploy the beans so I can then let the servlet go do it's thing? Should
I just do a shell script to force the initialization of the servlet
immediately following jboss loading. This doesn't really seem to warrant an
mbean.
Has anyone tackled something like this yet?
TIA,
John Moore
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
