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 separate small web app that gets auto-deployed and starts the main web app after unlocking the database, and stops it before shutting down the database; or (2) a second servlet within the web app to do the same thing (the main code is contained inside a single Struts-based servlet) However, in the first case, I can't see a way to have the one web app auto-deploy but not the other (seems to be host-specific, not context-specific); and in the second case, even without a <load-on-startup> element in the web.xml file for the main servlet, Tomcat still seems to initialize it at startup. (And even if it did, the docs say it would be auto-loaded as soon as its context URL was hit. No way to protect against that.) Am I missing something? I was hoping to do something outside of the main app, to keep it isolated from the database deployment details (there are at least two different configurations, only one of which needs the encryption), but if neither option is possible, I guess we will have to look at controlling the database startup and shutdown within the main app (which looks like it could be messy, what with all the stuff Hibernate, Spring, and Tomcat are doing behind the scenes for us). If anyone here has attempted something like this, I'd love to hear from you. Cheers, -- Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
