If you need to call the web service during startup, you could retry the call as long as you get a service-not-available error. Or you could find a way to synchronize the two webapps (e.g. using a shared class if they're always going to be on the same server). Or maybe you could load & cache the data when it's needed instead of loading it all at startup. -- Len
On Wed, Aug 13, 2008 at 18:41, Mathias P.W Nilsson <[EMAIL PROTECTED]> wrote: > > You are absolutly right. It's my wicket application that caches users from a > webservice on startup. But I guess I'll have to find a better solution. > > // Mathias > -- > View this message in context: > http://www.nabble.com/startup-order-for-deployment-tp18967318p18972567.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
