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 dat
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 - Use
You cannot control the order in which the webapps start. There are
ways that you can ensure the initialization is complete before your
webapp starts accepting requests, but first ask yourself: Why? Your
webapp must be able to handle the situation of the web service being
down, so is it really a pro
