"scott.stark(a)jboss.org" wrote : | I have moved it to PRE_REAL. Were not converting to the generalized deployer Ales is working on in the near term. | Moving it to PRE_REAL does not help aop. Basically, what is happening (and to summarize and hopefully get some feedback on my approach) is: *PARSE stage ** SchemaResolverDeployer parses the aop bean metadata from -aop.xml ** A yet to be created deployer parses the aop bean metadata from annotations using Ales's thingy. A few further points: - If using -aop.xml or aop annotations, an org.jboss.aop.microcontainer.beans.metadata.AOPDeployment is created. This is a subclass of AbstractKernelDeployment. - If using a beans.xml, an AbstractKernelDeployment is created *POST_CLASSLOADER stage ** A new deployer determines the AspectManager to be used based on classloader as before, and the aop bean metadata entries are "massaged" to reference the correct AspectManager. I also hope to be able to resolve the "duplicate interceptor entries in scoped deployments" problem I mentioned earlier in this layer. *PRE_REAL stage ** The AnnotationMetaDataDeployer loads all the classes in the deployment looking for annotations *REAL stage ** The AOPDeployment/AbstractKernelDeployment containing the aop bean metadata is deployed by the BeanMetaDataDeployer, resulting in the aop configuration being deployed to the AspectManager. None of this is committed, it is all work in progress on my machine. But basically we cannot load classes until after the BeanMetaDataDeployer has deployed the aop bean metadata. As before if I get rid of AnnotationMetaDataDeployer I do get some loadtime weaving. I have reopened http://jira.jboss.com/jira/browse/JBAS-5558 and assigned it to AS 5 CR2 since there is no way I will be able to finish this integration task by tomorrow and killing AnnotationMetaDataDeployer is a good enough workaround for me when working on this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154312#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...