User: janb    
  Date: 02/02/23 21:08:29

  Modified:    jetty/src/resources/jetty-plugin/META-INF jboss-service.xml
  Log:
  Added support for choice of Servlet2.3 or Java2 compliance for class loading 
delegation.
  
  Revision  Changes    Path
  1.21      +10 -3     
contrib/jetty/src/resources/jetty-plugin/META-INF/jboss-service.xml
  
  Index: jboss-service.xml
  ===================================================================
  RCS file: 
/cvsroot/jboss/contrib/jetty/src/resources/jetty-plugin/META-INF/jboss-service.xml,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- jboss-service.xml 21 Feb 2002 02:03:57 -0000      1.20
  +++ jboss-service.xml 24 Feb 2002 05:08:29 -0000      1.21
  @@ -32,6 +32,14 @@
       <attribute name="UnpackWars">true</attribute>
   
       <!-- ================================================================== -->
  +    <!-- If true, Jetty first delegates loading a class to the webapp's     -->
  +    <!-- parent class loader (a la Java 2). If false, Jetty follows the     -->
  +    <!--  Servlet 2.3 specification, and tries the webapp's own loader      -->
  +    <!-- first (for "non-system" classes)                                   -->
  +    <!-- ================================================================== -->
  +    <attribute name="Java2ClassLoadingCompliance">true</attribute>
  +
  +    <!-- ================================================================== -->
       <!-- If true, mbeans are created for Jetty and all contexts, logsinks,  -->
       <!-- listeners etc. View them via the JBoss management interface on     -->
       <!-- http://localhost:8082                                              -->
  @@ -44,9 +52,8 @@
       <!-- name="ConfigurationElement" attribute is a Jetty-style            -->
       <!-- configuration specification.  It is used to configure Jetty with  -->
       <!-- a listener on port 8080, and a HTTP request log location.         -->
  -    <!-- The placement of other Jetty XML configuration statements here is -->
  -    <!-- EXTREMELY DISCOURAGED: for example, any webapps deployed here     -->
  -    <!-- will NOT be visible to JBoss. If you REALLY NEED to specify       -->
  +    <!-- The placement here of other Jetty XML configuration statements    -->
  +    <!-- for deploying webapps etc is not encouraged: if you REALLY NEED   -->
       <!-- something extra, place it in WEB-INF/jetty-web.xml files          -->
       <!-- ================================================================= -->
   
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to