On Thu, Oct 15, 2009 at 11:53 AM, Peter Firmstone <[email protected]> wrote:
> It may be possible to segregate OSGi modules, into separate ClassLoaders > using bytecode dependency analysis and by capturing OSGi metadata. Unfortunately, this is harder than you might think. OSGi metadata provides a set of constraints, but often there are multiple solutions to those constraints, and sometimes the framework is not capable of resolving those constraints even if there is a solution available, since exhaustive checks are too expensive for large applications. What I am trying to say is; Being able to figure out how a particular framework implementation has wired up the class spaces, just by looking at the metadata is impossible, and likewise with bytecode dependency analysis. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug
