[jboss-jira] [JBoss JIRA] Created: (JBCL-77) Don't try to join with classloading space that does not exist

Adrian Brock (JIRA) jira-events at lists.jboss.org
Fri Dec 5 08:01:36 EST 2008


Don't try to join with classloading space that does not exist
-------------------------------------------------------------

                 Key: JBCL-77
                 URL: https://jira.jboss.org/jira/browse/JBCL-77
             Project: JBoss ClassLoader
          Issue Type: Bug
          Components: Dependencies
    Affects Versions: JBossCL.2.0.1.GA
            Reporter: Adrian Brock
            Assignee: Adrian Brock
             Fix For: JBossCL.2.0.2.GA, JBossCL.2.2.0.Alpha


If a classloading module has import-all=true we can't do a consistency check because its imports are not known.
This means the module has no classloading space.

Currently this leads to an NPE when such a module is resolved as an import of another module that is not imort-all=true
and it then tries to join with the non-existent space.

java.lang.NullPointerException
	at org.jboss.classloading.spi.dependency.ClassLoadingSpace.resolve(ClassLoadingSpace.java:325)
	at org.jboss.classloading.spi.dependency.ClassLoadingSpace.joinAndResolve(ClassLoadingSpace.java:122)

The joining should not happen if the resolved module doesn't belong to a classloading space,
i.e. import-all=true

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list