I did try setting the order of context tags. 
I assume that Catalina looks in server.xml before autodeploying apps from the 
webapps directory.

Thanks.



On Thursday 27 February 2003 05:00 pm, Will Hartung wrote:
> > From: "Ben Souther" <[EMAIL PROTECTED]>
> > Sent: Thursday, February 27, 2003 12:54 PM
> > Subject: startup order for applications
> >
> > I've got two applcations. The first is an Axis webservice application and
> > the second is a servelet/jsp app that consumes services from the first.
> >
> > I would like to configure the JSP app to make a webservice call to get
> > initialization params on startup. In order to do this, I need to insure
> > that the webservice app is up and running before the JSP app starts.
>
> Hmm...that's a bugger. You can't listen for the socket of the webservice,
> as it may not come up until after your dependent app is finished
> initializing.
>
> You can't "wait" for the other application, as if it's the first one to
> start up, it will block and the second webapp may never get a chance to
> initialize.
>
> Have you tried to see if the placement of the contexts within the
> server.xml is deterministic? i.e. The first context always starts before
> the next, or vice-a-versa? You might be able to glean some information from
> the source code about startup order.
>
> I doubt there is any way to ensure the startup order of arbitrarily placed
> webapps in the webapp directory. Those may be "auto-deployed" and
> initialized in the order they appear within the directory, which is
> internally unsorted and should be considered arbitrary.
>
> There isn't any portable way of ensuring webapp start up order, that I'm
> aware of at least.
>
> Let us know what works for you.
>
> Regards,
>
> Will Hartung
> ([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]

Reply via email to