Bug#341777: Support Mysql for WebApps deployed to Tomcat

2005-12-06 Thread Arnaud Vandyck
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kalle Kivimaa wrote: Andreas Schildbach [EMAIL PROTECTED] writes: 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

Bug#341777: Support Mysql for WebApps deployed to Tomcat

2005-12-06 Thread Andreas Schildbach
Kalle Kivimaa wrote: If a webapp wants to use a DB, it is up to the maintainer of that webapp package to decide which DB's s/he is going to support. Why don't you let the administrator decide upon the database? After all, that's what the SQL standard and the JDBC driver/JNDI datasource

Bug#341777: Support Mysql for WebApps deployed to Tomcat

2005-12-06 Thread Kalle Kivimaa
Arnaud Vandyck [EMAIL PROTECTED] writes: I'm not sure it's the responsability of JSPWiki to add symlinks in the tomcat5 directory tree. Well, it does so already :) It has to register itself as a webapp and it has to add a policy file. -- * Sufficiently advanced magic is indistinguishable from

Bug#341777: Support Mysql for WebApps deployed to Tomcat

2005-12-05 Thread Wolfgang Baer
tags 341777 + wontfix thanks Hi Andreas, Andreas Schildbach wrote: Package: tomcat5 Severity: wishlist If I have both packages tomcat5 and libmysql-java installed, I'd like to have the Connector/J driver availble for web applications installed into Tomcat, just as if I had copied the

Bug#341777: Support Mysql for WebApps deployed to Tomcat

2005-12-05 Thread Andreas Schildbach
Wolfgang Baer wrote: if you need stuff in your webapps you should put it in or link it from the webapps libs/classes directory to get it picked up. This is also some kind of security problem as common/lib is trusted. First of all, it is both common and recommended practise to _not_ include

Bug#341777: Support Mysql for WebApps deployed to Tomcat

2005-12-05 Thread Kalle Kivimaa
Andreas Schildbach [EMAIL PROTECTED] writes: I understand your point. Then what about a separate package just for the symlink? The package could depend on both tomcat(5|4) and libmysql-java, so it would disappear if either the database driver or tomcat is uninstalled. Umm, as far as I

Bug#341777: Support Mysql for WebApps deployed to Tomcat

2005-12-05 Thread Andreas Schildbach
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

Bug#341777: Support Mysql for WebApps deployed to Tomcat

2005-12-05 Thread Kalle Kivimaa
Andreas Schildbach [EMAIL PROTECTED] writes: 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,

Bug#341777: Support Mysql for WebApps deployed to Tomcat

2005-12-02 Thread Andreas Schildbach
Package: tomcat5 Severity: wishlist If I have both packages tomcat5 and libmysql-java installed, I'd like to have the Connector/J driver availble for web applications installed into Tomcat, just as if I had copied the driver to common/lib. Why don't you symlink from