You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@cocoon.apache.org by da...@cocoon.zones.apache.org on 2006/11/15 21:17:44 UTC
[DAISY] Updated: Shielded Classloading

A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1262.html

Document ID: 1262
Branch: main
Language: default
Name: Shielded Classloading (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 11/15/06 8:17:42 PM
Updated by: Carsten Ziegeler

A new version has been created, state: publish

Parts
=====

Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 2295 bytes (previous version: 2182 bytes)
Content diff:
    <html>
    <body>
    
--- <p>Shielded classloading is an optional feature of Cocoon which helps you in
--- avoiding typical problems with respect to class loading. Usually the servlet
--- container sets up a class loader for each web application. This class loader
--- works "parent-first" which means that whenever a class is loaded it is first
--- searched in the parent class loader of the web application class loader and only
--- if its not available there, it is loaded from the classes in WEB-INF/classes or
--- the jars in WEB-INF/lib. In general this is a useful mechanism which also allows
--- you to share classes between web applications by putting them in the parent
--- class loader (refer to the documentation of your application server/servlet
--- engine for more information).</p>
+++ <p class="note">This feature will hopefully part of the maven war plugin soon.
+++ </p>
    
+++ <p>Shielded classloading is an optional feature of the Cocoon deployer-plugin
+++ for Maven. It helps you in avoiding typical problems with respect to class
+++ loading. Usually the servlet container sets up a class loader for each web
+++ application. This class loader works "parent-first" which means that whenever a
+++ class is loaded it is first searched in the parent class loader of the web
+++ application class loader and only if its not available there, it is loaded from
+++ the classes in WEB-INF/classes or the jars in WEB-INF/lib. In general this is a
+++ useful mechanism which also allows you to share classes between web applications
+++ by putting them in the parent class loader (refer to the documentation of your
+++ application server/servlet engine for more information).</p>
+++ 
    <p>Unfortunately there are some problems with this approach: for example if the
    servlet engine has configured a logging framework like commons logging and
    exposes this  in the parent class loader for the web applications, than all web
(22 equal lines skipped)