From: "Adam Heath" <doo...@brainfood.com>
Additionally, the way the classloaders are constructed is a bit odd.
The bootstrap loader only has ofbiz.jar. The code then creates a
classloader will *all* jars in base/lib, recursively. After the
containers and components are started, yet another classloader is
created, this time with proper libs and all other ofbiz-$foo.jar.
Both of those classloaders update the java.class.path system property.
This is a bug, as the instrumentation changes all ofbiz-$foo.jar into
a new jar in /tmp, so the value of the property is different each
time. Additionally, the second created classloader should not load
the base component again, as that is sub-optimal.
I'm thinking that component code should really move to start.
Another bug, is that due to one of the above bugs, the first
classloader is not instrumented at all. Since this is the classloader
that contains framework/base, you don't see any line hits in the report.
Since the the start (my start with OFBiz) I have always wondered about
complexity there
Jacques
