[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 : 
  | I am thinking about if we need to create special classpools understanding the new loaders. Let's ignore this for now until I am sure that these pools will be needed

That was my original guess. i.e. we would have some kind of plugin
that would recognise the classloader type and use the metadata available from
the classloader (and the knowledge of its internal assumptions/mechanisms) to 
create the pools.

e.g. The default would just be a hierarchical version that looked at
ClassLoader.getParent() for the normal classloader rules
but there would be others that recognised the UCL and the new classloader
and asked them for how they are configured, e.g. which loader repository
or exported packages, etc.

But, like I said, I don't think the tying of the aop definition to the classloader
is the correct solution.

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

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