So in effect I'm deferring all interaction w/ RAM to be at request time and not startup time correct?
I guess I could even take it one step further (and easier to implement I think) where I build some static singleton initializer that manages an "am I loaded properly" flag and if not, loads its data (This is the RAM interaction) otherwise just handle the request normally. It adds an extra check but checking if( ApplicationStatus.IS_LOADED ) isn't such a big deal in the long run. That is unless we're not talking the same thing here. :) markt-2 wrote: > > JeanNiBee wrote: >> Hi >> >> I have two application contexts, /RAM and /UO. > > Context initialization is serial. If you try starting in the wrong order > you > will be out of luck. > > Tomcat won't start serving requests until all the contexts have started. > > You can't control the order the apps start in. It will be arbitrary. > > You could try the following: > > Add a filter to OU that is mapped to /*. It checks for RAM, it RAM isn't > running > the requests are blocked. Once RAM is running it lets requests through and > then > your Servlet inits. You could write your filter such that once it detects > RAM is > running, it doesn't check RAM again. > > Mark > > -- View this message in context: http://www.nabble.com/Application-Context-%28and-or%29-%3CSERVICE%3E-element-load-orders-when-starting-Tomcat-5-6.-tp24606540p24607746.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
