On Oct 6, 2006, at 7:00 AM, Ken Tam wrote:
Thoughts on the search order/priority for these classloader hierarchies? Child-before-parent has some real advantages here -- it lets extensions specify exactly what version of a dependency to use and expose to its consumers, rather than have the hosting environment potentially hose it by globally exposing an incompatible version.
The problem with child-before-parent is that it tends to cause too much isolation leading to problems sharing API classes. I'd tend to favour OSGi-type import/export for that kind of fine-grain control.
-- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
