I did a quick look at the jboss-classpool.
-
http://anonsvn.jboss.org/repos/jbossas/projects/jboss-classpool/
It looks like a big mess. :-)
I don't know enough about how it's actually implemented,
to properly say what should be spi.
But from what I saw, there is a lot of impl details that can be properly moved/hidden.
e.g.
Lets at least properly expose API - the code the user should touch,
everything else should be plugins == impl details, something user can only touch at his
own risk.
If there is some spi, I guess you can re-factor that as well,
but I must say I don't see a lot of interfaces that would be really intended to help
the dev change the behavior.
They are mostly there to have good abstraction over the impl.
Perhaps you could also join in together the code for 4.x and 5.x:
* jboss4, ucl --> jboss4/pool, jboss4/cl
* jboss5, jbosscl --> jboss5/pool, jboss5/cl
Or whatever you feel fits pool and cl better.
e.g. cl could be called structure
And I guess we can do some simple "cleanup" of root org.jboss.classpool
package.
e.g. some split into pool, resource-plugins, strategy, ...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247575#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...