On Sun, 10 Nov 2002 21:34, Paul Hammant wrote: > Should not we split avalon-framework.jar into avalon-framework.api.jar > and avalon-framework-refimpl.jar ?
I don't think there is any need to separate implementations that have no external dependencies as often most of my "client" objects are also "server" objects and use DefaultComponentManager etc. However currently I am using a separation based on whether or not the classes have external dependencies. For example the following classes all got moved to the "-ext" jar. So essentially anything that directly refences Logkit/Log4j/Xalan will get migrated to this jar. I figured that the SAX stuff is broadly deployed enough that we need not bother separating it out. The reason for this separation is that it enables clean classloader trees. I have a Phoenix fork that does this to good effect and have a tree in avalon that already has the changes. I want to let it settle for a while and experiment with things before committing it though. -- Cheers, Peter Donald *------------------------------------------------------* | An expert is someone who knows everything about the | | topic except for its place in the world. | *------------------------------------------------------* -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
