"kabir.khan(a)jboss.com" wrote : Because the beans that push the things into the
aspectmanager are not deployed until the BeanMetaDataDeployer picks them up in the REAL
stage.
|
| Are you suggesting that as part of my POST_CLASSLOADER deployer rip out the aop
beanmetadatafactories from the deployment, and deploy them myself there? That could work,
they are easily identifiable, but I didn't want to mess around with the deployment too
much.
You at least need to push the point-cut definitions into the AspectManager
during POST_CLASSLOADER so you know which classes need weaving and where.
The aspects themselves won't become usable until the dependencies are
satisifed (i.e. dependencies get injected onto them during the REAL stage)
but then nobody should be trying to use the objects until this is done
(they should just be analysing the classes).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154420#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...