On Wed, May 12, 2004 at 07:18:01PM +0100, Paulo Lopes wrote:No, that's not quite what i need. I've 2 webapps, one if a frontend end to my application that is served to the internet, the other one is a "backoffice" to manage the frontend that is available only to the intranet. Both have distinct security configurations and roles applied to users and i need to keep the separated.
Hi,
I've 2 webapps on my tomcat, 3 counting with openejb_loader-0.9.2, and one of my webapps has a servlet that is run on start-up. This servlet invokes a class wich was supposed to access some Session EJB deployed into OpenEJB.
The problem is that since tomcat loads first my webapps and later the openejb_loader webapp all EJB's beans and other classes such as javax.ejb.* aren't available to my servlet.
How can i force openejb_loader to be the first webapp to load? i've tryed to define it in server.xml but with no sucess.
Any thoughts on how to do this?
Hi Paulo,
Question for you on this note; if you could have one OpenEJB per webapp rather than one global to all webapps, would that be closer to what you really want?
I've put some work into allowing people to have one OpenEJB per
webapp, so if that is really what you want I'll see if I can get
something to you.
The frontend works fine because it only needs to use EJB's per user request, so at that time, openejb_loader webapp is already running.
The backoffice, has a simple scheduler that runs tasks at a given time, so it is started with a servlet with the "load-on-startup" tag, and here is the problem, if a task is run on load or at the time that the server is starting, tomcat might have not started openejb_loader webapp yet.
I've tryed that, no success.Otherwise, have you tried changing the priorities on the other webapps to be lower (e.g. above 0) than the loader's priority?
If that doesn't work, you could add the loader.jar and related servletHow many openejb servers would be available? 1 or 2?
to each of the webapps and delete the openejb_loader webapp
completely.
-David
Paulo
