Re: STOP INCLUDING EXTERNAL JARS IN YOUR JAVA PACKAGES!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ola Lundqvist <opal@debian.org> writes:
<snip>
> You say that the war-files allow the classloading. That is not entirely
> true. Take tomcat for example.
>
> * You place a war-file in the specified directory.
>
> * Restart tomcat.
>
> * Tomcat now unzips this file to the webapp directory.
>
> * Tomcat is started and uses the directories that has the WEB-INF dirs
> and more.
>
> Conclusion: The war-file is not used directly. It is mearly unzipped and
> because we have a deb arproach in debian the war-files is not needed.
>
> War files have a major disadvantage and that is that they are simple zip-
> archives which means that they will not support symbolic links.
>
> I think we should cover the war-files in the policy too.
> They should be avoided, right?
<snip>
I don't understand your point. The important thing here is that the CLASSPATH
is not updated and the System ClassLoader is not used. Tomcat uses an adaptive
classloader so that WEB-INF/lib/*.jar files are specific to each Web
Application.
Thus we have the ability to run incompatible libs in different applications in
the SAME VM. Pretty cool!
Kevin
- --
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
Location - San Francisco, CA, Cell - 415.595.9965
Jabber - burtonator@jabber.org, Web - http://relativity.yi.org/
Copyright exists to improve science not to preserve the rights of the author.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt
iD8DBQE77ZRfAwM6xb2dfE0RAh/+AKCFxC70YVlew59k9uyVKddXE/UPrwCg0nua
q2CeU1E1voAMjFzy6DUPhd8=
=w9wN
-----END PGP SIGNATURE-----
Reply to: