AM
To: Tomcat Users List
Subject: Re: Selective auto-deploy of web-apps?
Or IMHO, use a request filter to check for the database and then
redirect the use to a "not available" or "out of order" page. This can
easily happen before any processing starts and the servlet need not be
quot;Caldarale, Charles R" <[EMAIL PROTECTED]>:
From: Michael Hackett [mailto:[EMAIL PROTECTED]
Subject: Re: Selective auto-deploy of web-apps?
Anyway, I appreciate the attempt, but I don't think that solves my
problem of controlling the startup of a webapp or servlet from a
Quoting "Caldarale, Charles R" <[EMAIL PROTECTED]>:
> > From: Michael Hackett [mailto:[EMAIL PROTECTED]
> > Subject: Re: Selective auto-deploy of web-apps?
> >
> > Anyway, I appreciate the attempt, but I don't think that solves my
> > proble
> From: Michael Hackett [mailto:[EMAIL PROTECTED]
> Subject: Re: Selective auto-deploy of web-apps?
>
> Anyway, I appreciate the attempt, but I don't think that solves my
> problem of controlling the startup of a webapp or servlet from another
> webapp or servlet.
I d
> From: "Caldarale, Charles R" <[EMAIL PROTECTED]>
>
> > From: Michael Hackett [mailto:[EMAIL PROTECTED]
> >
> > We want to prompt the user for the database password and
> > boot the database before launching the real application.
>
> What user?
The user of the web app. In this case, there wil
Bonjour Michael
Have you looked into using Spring Framework lazy-init=true property e.g
?
Martin-
- Original Message -
From: "Michael Hackett" <[EMAIL PROTECTED]>
To:
Sent: Thursday, December 08, 2005 5:08 PM
Subject: Selective auto-deploy of web-apps?
I'm t
> From: Michael Hackett [mailto:[EMAIL PROTECTED]
> Subject: Selective auto-deploy of web-apps?
>
> We want to prompt the user for the database password and
> boot the database before launching the real application.
What user?
> I guess we will have to look at contro
I'm trying to come up with a solution for the following situation: We
have a webapp that we need to deploy with an encrypted Derby database.
We want to prompt the user for the database password and boot the
database before launching the real application. I was thinking of having
either:
(1) a sepa
