[jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: ClassLoading Module usage

[adrian@jboss.org]

I don't like either of these. :-)

"kabir.khan at jboss.com" wrote : 
  | Without clearing the black list, the new class is never picked up. Can we include a method to do this in the spi? We would not even need to clear the whole set, just a particular entry. The domain already has a method for this, but I need it on BaseClassLoader.
  | 

It shouldn't be blacklisting at all if classes can suddenly appear.
This just needs adding to the ClassLoaderMetaData, i.e. whether
caching and blacklisting can be done for the classloader.

anonymous wrote : 
  | Another problem is if a generated AOP proxy is not in the same package as the proxied class (e.g. if the proxied super class is in the java.lang package, we create a proxy in the default package instead). This causes a problem since the underlying ClassLoaderDomain.classLoadersByPackageName does not get updated to include the default package, so the class is never found. 

Adding this, would mean people can play around things in dangerous ways
(like the URLClassLoader.addURL() that I want to avoid).

It's also not going to work with the OSGi style rules where you are explicitly
importing/exporting package names.

Why aren't the java.* enhancements added to the root classloader?
This would seem like the more sensible location to control overriding standard
classes and it would just be one place to say it always "exports" the default package.

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

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