JBoss development,
A new message was posted in the thread "ScopedClassPoolRepositoryImpl and default
ClassPool":
http://community.jboss.org/message/528638#528638
Author : Flavia Rainone
Profile :
http://community.jboss.org/people/flavia.rainone@jboss.com
Message:
--------------------------------------------------------------
mailto:flavia.rainone@jboss.com wrote:
I'm calling that new module scoped-classpool. Once it is ready, we can decide whether
it would be a good idea to use those changes as a patch for Javassist, or whether we wanna
keep it the way it is.
That new module is created. I removed everything that I
thought is no longer being used, and replaced all references to javassist.scopedpool
classes by references to the new org.jboss.classpool.scoped classes.
A summary of what has been done can be obtained by looking at the svn history log:
- Copied Scoped ClassPool classes from Javassist to a new scopedpool module.
- ScopedCPRepository is no longer singleton, it is an abstract class with a protected
constructor instead. The default class pool can be defined as a parameter of the
constructor.
- Replaced all references to javassist.scopedpool package by org.jboss.classpool.scoped
package.
- Deleted ScopedClassPoolFactoryImpl class
Now I'm open for suggestions on what should be the next step: to write a patch for
Javassist; to do an alpha release of the new version and update depending projects (JBoss
AOP and JBoss Reflection, besides deployers-vfs tests); or to do more refactoring and
improve something that doesn't look ok.
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/528638#528638