I have added a patch for adding shielded classloading for single blocks
(http://issues.apache.org/jira/browse/COCOON-1955). This allows you to
shield certain blocks from other blocks inside your Cocoon application,
which is necessary when there are conflicting versions of Java libs that
cannot be resolved without patching external code.
For that I modified the BootstrapClassLoaderManager slightly (and stuff
from the blocks-fw). The configuration for a shielded block also uses
the ShieldingServlet. Does this conflict with the upcoming move of the
shielding stuff into the maven-war-plugin?
Alex
Carsten Ziegeler schrieb:
Hi,
I extracted our support for shielded classloading and added a patch
to the maven war plugin, see http://jira.codehaus.org/browse/MWAR-84.
As soon as this patch is accepted by the maven community (and hopefully
they will), shielded class loading is not the concern of Cocoon anymore
and we can remove this stuff from our own plugin.
To prepare this, I committed the code I used for the war plugin to our
deployer plugin - so we are now using a simplified version if the
classloading which does not depend on the bootstrap stuff anymore.
This has the advantage of removing the bootstrap module and move the
stuff into core again. I think we should move the basic class loading
support into core while moving the reloading stuff into a separate
module to keep the core dependencies as minimal as possible.
Carsten
--
Alexander Klimetschek
http://www.mindquarry.com
