On Apr 7, 2006, at 7:21 PM, John Sisson wrote:
Dain Sundstrom wrote:
Unpacked archives in the repository:
The solution is to not place unpacked archives in our repository.
I (dain) am going to look at using a class loader that can read
from classes and resources from jars nested in jars. Assuming we
can find or write a class loader such a class loader, we will need
to assure that Tomcat and Jetty can work from a packed archive.
Also need to ensure/test that a security manager policy file can
grant permissions for all JARS in a CAR or individual nested JARs
using a codebase URL in the policy file so users have the same
level of control they would have had in the config-store (at the
same time solving the issue with the policy files needing to be
changed due to the numbered directories in the config-store):
http://mail-archives.apache.org/mod_mbox/geronimo-user/200602.mbox/%
[EMAIL PROTECTED]
I'm planing starting with the emory university resource class loader
which supports all the security stuff like URLClassLoader, but is
public domain and much more modular. Specifically, I think it will
be easy to implement nested jar support via unpacking to a temp
directory.
-dain
