Kalle Kivimaa wrote:
Umm, as far as I understand the Debian packaging policy, this would be a severe violation of "no unneccesary package bloat" -policy. Dozens of lines of code for a simple ln -s. IMO it is the responsibility of the webapp package requiring database access to manage any symlinks, not of Tomcat, not of the database, nor a specialized Tomcat DB package.
I'm afraid I don't know about the packaging policy. I can only say that the webapp can't know what database the server-admin or deployer is going to use, especially since in the Realm case he's got the option of an in-memory or file-based realm, requiring no database at all. If you look at the J2EE specification, all the application needs to know is the path to a JNDI Data Source. Webapps should not contain specific database drivers, nor the URL to a database, nor any database login information. This is all configured in the JNDI context provided by the servlet container (or application server).
Look at the options: If there is not going to be a package like this, the only option right now would be to manually copy the database driver to common/lib or manually creating a symlink there. Doesn't this practice also stand against the idea of Debian? The symlink created this way could be dangling, too. Common/lib could be exposed via /etc, where the user is "allowed" to put configuration. I would still prefer the packaging solution.
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
