User: jules_gosnell
  Date: 02/03/15 17:00:12

  Modified:    jetty/src/resources/jetty-plugin/META-INF jboss-service.xml
  Log:
  refactor JettyService:
  - bind Jetty more closely to JBoss Service lifecycle
  - now that jetty.xml is contained in jboss-service.xml setPublishMBeans cannot work 
- removed
  
  Revision  Changes    Path
  1.25      +1 -8      
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.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- jboss-service.xml 27 Feb 2002 09:24:25 -0000      1.24
  +++ jboss-service.xml 16 Mar 2002 01:00:12 -0000      1.25
  @@ -37,15 +37,8 @@
       <!--  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                                              -->
  -    <!-- ================================================================== -->
   
  -    <attribute name="PublishMBeans">true</attribute>
  +    <attribute name="Java2ClassLoadingCompliance">true</attribute>
   
       <!-- ================================================================= -->
       <!-- Configuring Jetty. The XML fragment contained in the              -->
  
  
  

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

Reply via email to