-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All,
While reading another thread ("What's going on ... ?"), I started to
think about how inconvenient it is to have to put your JDBC driver into
the server's lib directory. As it stands, now, all webapps must share
the same version of the same driver, and the main installation of Tomcat
(or scion, when using CATALINA_BASE) must be modified from the default
in order to deploy your application :(
It would seem to me that, if the webapps's META-INF/context.xml file
defines a JNDI <Resource>, that the server could use the context's
libraries to initialize those resources.
If the above were possible, then a web application could really be
self-contained. That would allow different webapps deployed onto the
same server to use different JDBC drivers for the same (type of)
database, which would be really nice.
Can any of the Tomcat wonks comment on the possibility of using the
WebappClassLoader to initialize JNDI resources? I suppose this would
also touch on the subject of JNDI DataSources never being closed, since
using the WebappClassLoader without closing those resources would create
a costly resource leak.
Thanks,
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkwk0wQACgkQ9CaO5/Lv0PC1CACglg/R97/A6aZ5DD90g4gEM72M
mu4An3CYQVCgVgHVwkD3Pw4HpuDE5g1Z
=n95V
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
