The case is still that most servlet containers, Tomcat included, are multithreaded and order of processing should not be counted on. One app may be swapped out while the other app runs. It is far better to write your servlets so that there is no dependency on order of operation, order of parameters, etc. Another reason not to count on this is that it is not part of the specification and one implementation or version of a container may choose to provide order or not and this might change. There have been many recommendations on how to do this and I would suggest you try them. Your apps will probably end up being more scaleable as well.
Robert S. Harper Information Access Technology, Inc. -----Original Message----- From: Jilles van Gurp [mailto:[EMAIL PROTECTED] Sent: Thursday, September 15, 2005 11:52 AM To: Tomcat Users List Subject: Re: Order of WebApp Loading If you define the contexts in the server.xml, they are started in the order that you define them, I think. Regards, Jilles Peter Menzel wrote: > Hi there, > > I have a question concerning Tomcats webapp loading: > What is the order in which tomcats loads its webapps ? > I have two webapps configured by /conf/Catalina/localhost/XXX.xml and > I need one webapp to be loaded before the other, because it starts the > database. > How does Tomcat choose the first, second, ... > And what is the loading sequence, if both are deployed as a .war ? > > Kind regards, Peter Menzel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
