The scoped AspectDeployer and AspectManager deploy correctly, as I previously said.
The problem comes from the fact that there is no way (or I don't now of any) to defer the deployment of an embedded -aop.xml file until all services from that deployment unit are started. Because of that, my jms-aop.xml will be deployed by the jboss-aop.deployer "jboss.aop:service=AspectDeployer" and my aspects will go to "jboss.aop:service=AspectManager", because my own AspectDeployer will be only registered with the MainDeployer AFTER jms-aop.xml finds its deployer.
My solution was to create a helper service (AspectLoader) and use it to explicitely deploy aspects with my AspectDeployer. jms-aop.xml also gets deployed by "jboss.aop:service=AspectDeployer", but that's secondary, since I won't look up my aspects there.
I would have attached a working example, if forums permitted that.
IF you know a more elegant solution, please let me know.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883607#3883607
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883607
|
