[jboss-cvs] JBossAS SVN: r91037 - branches/dml-log-service-integration/varia/src/resources/logging.

[jboss-cvs-commits at lists.jboss.org]

Author: david.lloyd at jboss.com
Date: 2009-07-09 23:14:39 -0400 (Thu, 09 Jul 2009)
New Revision: 91037

Modified:
   branches/dml-log-service-integration/varia/src/resources/logging/logmanager-jboss-beans.xml
Log:
Comment logmanager-jboss-beans.xml; also add AS support for per-deployment log configs

Modified: branches/dml-log-service-integration/varia/src/resources/logging/logmanager-jboss-beans.xml
===================================================================
--- branches/dml-log-service-integration/varia/src/resources/logging/logmanager-jboss-beans.xml	2009-07-10 03:09:49 UTC (rev 91036)
+++ branches/dml-log-service-integration/varia/src/resources/logging/logmanager-jboss-beans.xml	2009-07-10 03:14:39 UTC (rev 91037)
@@ -24,6 +24,7 @@
 
 <deployment xmlns="urn:jboss:bean-deployer:2.0">
 
+   <!-- These two beans are to create the deployer for logging config files. -->
    <bean name="JBossLoggingMetaDataFactoryDeployer" class="org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryDeployer">
       <constructor>
          <parameter>org.jboss.logging.metadata.LoggingMetaData</parameter>
@@ -38,11 +39,36 @@
       <property name="registerWithJBossXB">true</property>
    </bean>
 
+   <!--
+     ~ This is the system logging context, which is the default log context.  It is "started" on demand so that it
+     ~ the dependency (JBossLogService, below) isn't started until a jboss-logging.xml is deployed; in reality
+     ~ the backing object is present from the moment the log system is initialized in bootstrap.
+     -->
    <bean name="Logging:CONTEXT:system" class="org.jboss.logmanager.LogContext" mode="On Demand">
       <constructor factoryClass="org.jboss.logmanager.LogContext" factoryMethod="getSystemLogContext"/>
       <depends>JBossLogService</depends>
    </bean>
 
+   <!--
+     ~ This is the log service, which removes the bootstrap logging configuration when a logging configuration
+     ~ is deployed (but only for the system log context; a deployment to another context will not cause this service
+     ~ to start).
+     -->
    <bean name="JBossLogService" class="org.jboss.logmanager.LogService" mode="On Demand"/>
 
+   <!-- This is the repository selector for log4j which causes it to bridge to the logmanager. -->
+   <bean name="JBossLog4jRepostiorySelector" class="org.jboss.logmanager.log4j.BridgeRepositorySelector"/>
+
+   <!--
+     ~ These two beans define the per-classloader log context selector which allows per-deployment logging.  Since
+     ~ enabling this feature may have a performance impact in certain cases, it's started up lazily (on demand)
+     ~ when a separate log context is defined in a user deployment.
+     -->
+   <bean name="JBossLogManagerClassLoaderContextSelector" class="org.jboss.logmanager.ClassLoaderLogContextSelector"/>
+
+   <bean name="JBossLogManagerContextSelectorService" class="org.jboss.logmanager.LogContextSelectorService" mode="On Demand">
+      <property name="selector">
+         <inject bean="JBossLogManagerClassLoaderContextSelector"/>
+      </property>
+   </bean>
 </deployment>