[jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Reimplementing AspectManager/Domains to understand jboss

[adrian@jboss.org]

I'm not following what problem you are trying to solve?

If a class isn't visible using the classloader rules then you shouldn't be able
to use AOP to change that. 

e.g. In your final comment where you want a "global" aspect definition then
the deployments that want to use it would need to "import" the classloader
where those aspects are deployed.

I thought the issue for you was just how you attach the aop domains to the
shared classloader spaces (either the old import-all rules or imports).
Doesn't the getClassLoaderFor() stuff solve this?

if the issue is mainly an ease-of-use thing, i.e. allowing people to share
config where part of the config contains classes that are not visible but are
irrelevant then that's really your choice.

e.g. Do you still allow this to work where pkg.a is invisible.
You could ignore the fact that PojoA cannot be loaded from a deployment because
it is not relevant to an application using pkg.b?


  | <bind pointcut="all(pkg.a.PojoA) OR all(pkg.b.PojoB)">
  |    <interceptor name="pkg.b.MyInterceptor"/>
  | </bind>
  | 

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

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