[
http://jira.jboss.com/jira/browse/JBMICROCONT-223?page=all ]
Adrian Brock closed JBMICROCONT-223.
------------------------------------
Resolution: Done
This has been fixed by handling getPackage(s) requests using similar rules
to the class and resource delegation.
Sealing violation checking has been added.
Package handling not working properly in new classloader
--------------------------------------------------------
Key: JBMICROCONT-223
URL:
http://jira.jboss.com/jira/browse/JBMICROCONT-223
Project: JBoss MicroContainer
Issue Type: Bug
Components: General
Affects Versions: JBossMC-2.0.0.Beta7
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossMC-2.0.0.CR1
The package handling is not working properly in the new classloader.
1) In the new classloader each classloader has no parent (unlike the old
UnifiedClassLoader - UCL).
Instead the parent is a Loader. This means that packages in the parent (e.g. the
classpath) are not visible
2) In both the old and new classloader, packages are not retrieved across the peers
this means that each classloader gets its own package object.
This means that package sealing does not work.
3) Since the sealing check is in the URLClassLoader, the new classloader is not
performing
this check - it uses the SecureClassLoader
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira