[jboss-jira] [JBoss JIRA] Closed: (JBAS-6032) Refactor AOPClassLoaderDeployer

Refactor AOPClassLoaderDeployer -------------------------------- Key: JBAS-6032 URL: https://jira.jboss.org/jira/browse/JBAS-6032 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public(Everyone can see) Components: AOP Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossAS-5.0.0.GA From devlist http://lists.jboss.org/pipermail/jboss-development/2008-October/012613.html Kabir, can you modify your deployer to specify java.lang.ClassLoader as an input instead of using the relative ordering. Also this deployer says it needs a VFS deployment. Other than the names used within AOP; ScopedVFSClassLoaderDomain VFSClassLoaderDomainRegistry I don't see any dependency on the VFS api? It might have done in the past until we refactored the way in the memory url part of the classpath is done? Finally, this still hasn't been updated to understand how subdeployment classloaders work. It should be asking whether the (sub-)deployment has an org.jboss.classloading.spi.dependency.Module attachment and hence its own classloader. Even the old code which has some hardwiring for JBossWebMetaData looks broken since it only unregisters top level deployment classloaders in undeploy() ?