"alesj" wrote :
| "adrian(a)jboss.org" wrote :
| | I think a better integration point would be to have a Spring aop deployer like
| | our aop deployer to analyse (and in your case modify) the classloader
| | based on metadata?
| Could be done, but I don't see what this brings over their per app server
approach.
Because if I understand what this doing (almost certainly a bad assumption :-)
Then its only going work properly simple cases like in web-apps or scoped ears.
In other environments where applications share a classloading space,
e.g. import-all=true or osgi style imports
the aop config needs to be shared/merged, otherwise point cut expressions won't get
applied
to caller classes in other applications.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222696#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...