[jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP asintegration WITHOUT the integration :-)

[adrian@jboss.org]

"kabir.khan at jboss.com" wrote : "adrian at jboss.org" wrote : "adrian at jboss.org" wrote : 
  |   |   | My preferred solution to use the scopes. i.e. you can choose
  |   |   | to deploy aop config at the SERVER, SUBSYSTEM, APPLICATION level, etc.
  |   |   | but this requires doing a lot work fixing everything to make sure
  |   |   | it sets the correct thread local MetaData for AOP to know which Scope
  |   |   | applies at runtime.
  |   |   | 
  |   | 
  |   | This thead local is really just a generalization of ejbs/mbeans
  |   | setting the correct context classloader and java:/comp/env
  |   | 
  |   | In principle once this is done. The only work required by AOP
  |   | would be for the deployer to create hierarchical ...
  |   | 
  | 
  | Is this work in progress? Or please let me know how I can help make this happen.
  | 

It's not work in progress, at least not yet. 
I only added the deployments scope a week ago.

I'd suggest you try it yourself with a mock test, e.g. write an aspect
that pushes the metadata from the advisor onto the stack and test it using
the aop proxy where you can pass in the metadata.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082057#4082057

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082057