User: user57
Date: 01/08/16 11:15:56
Modified: src/etc/conf/default jboss.jcml
Log:
o tidied up comments some
Revision Changes Path
1.60 +138 -102 jboss/src/etc/conf/default/jboss.jcml
Index: jboss.jcml
===================================================================
RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/jboss.jcml,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- jboss.jcml 2001/08/16 05:23:36 1.59
+++ jboss.jcml 2001/08/16 18:15:56 1.60
@@ -7,12 +7,12 @@
<!-- -->
<!-- ===================================================================== -->
-<!-- $Id: jboss.jcml,v 1.59 2001/08/16 05:23:36 d_jencks Exp $ -->
+<!-- $Id: jboss.jcml,v 1.60 2001/08/16 18:15:56 user57 Exp $ -->
<!--
| This is where you can add and configure your MBeans.
|
- | ATTENTION:
+ | *ATTENTION*
|
| The order of the listing here is the same order as
| the MBeans are loaded. Therefore if a MBean depends on another
@@ -23,7 +23,7 @@
<server>
<!-- ==================================================================== -->
- <!-- Classloading -->
+ <!-- Class Loading -->
<!-- ==================================================================== -->
<mbean code="org.jboss.web.WebService"
@@ -58,9 +58,11 @@
-->
</mbean>
- <!-- Uncomment to use Tyrex (tyrex.exolab.org) transaction manager plugin
- instead of the org.jboss.tm.TransactionManagerService and comment out
- the TransactionManagerService above
+ <!--
+ | Uncomment to use Tyrex (tyrex.exolab.org) transaction manager plugin
+ | instead of the org.jboss.tm.TransactionManagerService and comment out
+ | the TransactionManagerService above.
+ |
<mbean code="org.jboss.tm.plugins.tyrex.TransactionManagerService"
name="DefaultDomain:service=TransactionManager">
<attribute name="ConfigFileName">../conf/default/domain.xml</attribute>
@@ -121,10 +123,11 @@
name="JCA:service=RARDeployer">
</mbean>
- <!-- Minerva no transaction connection manager factory.
-
- Use this for resource adapters that don't support
- transactions. -->
+ <!--
+ | Minerva no transaction connection manager factory.
+ |
+ | Use this for resource adapters that don't support transactions.
+ -->
<mbean code="org.jboss.resource.ConnectionManagerFactoryLoader"
name="JCA:service=ConnectionManagerFactoryLoader,name=MinervaNoTransCMFactory">
<attribute name="FactoryName">MinervaNoTransCMFactory</attribute>
@@ -134,10 +137,11 @@
<attribute name="Properties"></attribute>
</mbean>
- <!-- Minerva local transaction connection manager factory.
-
- Use this for resource adapters that support "local"
- transactions. -->
+ <!--
+ | Minerva local transaction connection manager factory.
+ |
+ | Use this for resource adapters that support "local" transactions.
+ -->
<mbean code="org.jboss.resource.ConnectionManagerFactoryLoader"
name="JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory">
<attribute name="FactoryName">MinervaSharedLocalCMFactory</attribute>
@@ -147,10 +151,11 @@
<attribute name="Properties"></attribute>
</mbean>
- <!-- Minerva XA transaction connection manager factory
-
- Use this for resource adapters that support "xa"
- transactions. -->
+ <!--
+ | Minerva XA transaction connection manager factory
+ |
+ | Use this for resource adapters that support "xa" transactions.
+ -->
<mbean code="org.jboss.resource.ConnectionManagerFactoryLoader"
name="JCA:service=ConnectionManagerFactoryLoader,name=MinervaXACMFactory">
<attribute name="FactoryName">MinervaXACMFactory</attribute>
@@ -159,17 +164,20 @@
</attribute>
<attribute name="Properties"></attribute>
</mbean>
-
- <!-- Example database connections using resource adapters. The first is
- incomplete -->
- <!-- This is an example of using a resource adapter that supports XA
- transactions. The Minerva XA resource adapter requires an
- XADataSource to be in JNDI somewhere. JBoss doesn't include a
- database with an XA-compliant JDBC driver, so this will need to
- be configured to use whatever XADataSource implementation you
- have.
+ <!--
+ | Example database connections using resource adapters.
+ | The first is incomplete.
+ -->
+ <!--
+ | This is an example of using a resource adapter that supports XA
+ | transactions. The Minerva XA resource adapter requires an
+ | XADataSource to be in JNDI somewhere. JBoss doesn't include a
+ | database with an XA-compliant JDBC driver, so this will need to
+ | be configured to use whatever XADataSource implementation you
+ | have.
+ |
<mbean code="org.jboss.resource.ConnectionFactoryLoader"
name="JCA:service=ConnectionFactoryLoader,name=XAMinervaDS">
<attribute name="FactoryName">XAMinervaDS</attribute>
@@ -236,7 +244,11 @@
<attribute name="Trace">false</attribute>
</mbean>
-<!-- XADataSourceLoader is now deprecated. It now converts to
ConnectionFactoryLoader mbeans. See below for brief instructions
+ <!--
+ | XADataSourceLoader is now deprecated.
+ | It now converts to ConnectionFactoryLoader mbeans. See below for brief
+ | instructions.
+ |
<mbean code="org.jboss.jdbc.XADataSourceLoader"
name="DefaultDomain:service=XADataSource,name=DefaultDS">
<attribute name="PoolName">DefaultDS</attribute>
<attribute
name="DataSourceClass">org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl</attribute>
@@ -256,33 +268,38 @@
<attribute name="LoggingEnabled">false</attribute>
<attribute name="MaxIdleTimeoutPercent">1.0</attribute>
<attribute name="MinSize">0</attribute>
- </mbean>-->
-
-<!--This ConnectionFactoryLoader configuration was generated from the preceding
-XADataSourceLoader configuration with the "migration" XADataSourceLoader.
-To convert your XADataSourceLoaders, follow these steps.
-
-1. Make sure the resource adapter mbeans rardeployer and the three
-ConnectionManagerFactoryLoaders are in this file before any
-XADataSourceLoaders, as in this particular file.
-
-2. Start jboss.
-
-3. Make sure there is a jboss-auto.jcml file in conf/default (or wherever
-you are running from)
-
-4. Using the ConfigurationService mbean display (port 8082) press the
-SaveConfiguration button. This will save your configuration including
-the converted mbeans to jboss-auto.jcml.
-
-5. Look through jboss-auto.jcml and copy the ConnectionFactoryLoader
-mbeans corresponding to your XADataSourceLoader mbeans to this file.
-Clean up the indentation and comment out or remove the XADataSourceLoader mbeans.
-
-You can keep running with your XADataSourceLoader mbeans...
-but they will go away in a future jboss release. Why not convert now? -->
+ </mbean>
+ -->
- <mbean code="org.jboss.resource.ConnectionFactoryLoader"
name="DefaultDomain:service=ConnectionFactoryLoader,name=DefaultDS">
+ <!--
+ | This ConnectionFactoryLoader configuration was generated from the
+ | preceding XADataSourceLoader configuration with the "migration"
+ | XADataSourceLoader. To convert your XADataSourceLoaders, follow these
+ | steps:
+ |
+ | 1. Make sure the resource adapter mbeans rardeployer and the three
+ | ConnectionManagerFactoryLoaders are in this file before any
+ | XADataSourceLoaders, as in this particular file.
+ |
+ | 2. Start jboss.
+ |
+ | 3. Make sure there is a jboss-auto.jcml file in conf/default (or
+ | wherever you are running from)
+ |
+ | 4. Using the ConfigurationService mbean display (port 8082) press the
+ | SaveConfiguration button. This will save your configuration
+ | including the converted mbeans to jboss-auto.jcml.
+ |
+ | 5. Look through jboss-auto.jcml and copy the ConnectionFactoryLoader
+ | mbeans corresponding to your XADataSourceLoader mbeans to this file.
+ | Clean up the indentation and comment out or remove the
+ | XADataSourceLoader mbeans.
+ |
+ | You can keep running with your XADataSourceLoader mbeans...
+ | but they will go away in a future jboss release. Why not convert now?
+ -->
+ <mbean code="org.jboss.resource.ConnectionFactoryLoader"
+ name="DefaultDomain:service=ConnectionFactoryLoader,name=DefaultDS">
<attribute name="Properties">#
#Wed Aug 15 16:17:29 EDT 2001
ConnectionURL=jdbc\:HypersonicSQL\:hsql\://localhost\:1476
@@ -306,7 +323,9 @@
GCEnabled=false
MaxIdleTimeoutPercent=1.0
</attribute>
- <attribute
name="PrincipalMappingClass">org.jboss.resource.security.ManyToOnePrincipalMapping</attribute>
+ <attribute name="PrincipalMappingClass">
+ org.jboss.resource.security.ManyToOnePrincipalMapping
+ </attribute>
<attribute name="PrincipalMappingProperties">#
#Wed Aug 15 16:17:29 EDT 2001
userName=sa
@@ -341,7 +360,6 @@
</mbean>
-
<!-- ==================================================================== -->
<!-- JBoss Server Management -->
<!-- ==================================================================== -->
@@ -355,21 +373,13 @@
<!-- ==================================================================== -->
- <!-- J2EE deployment -->
+ <!-- Web Container -->
<!-- ==================================================================== -->
- <mbean code="org.jboss.ejb.ContainerFactory"
- name=":service=ContainerFactory">
- <attribute name="VerifyDeployments">true</attribute>
- <attribute name="ValidateDTDs">false</attribute>
- <attribute name="MetricsEnabled">false</attribute>
- <attribute name="VerifierVerbose">true</attribute>
- <attribute name="BeanCacheJMSMonitoringEnabled">false</attribute>
- </mbean>
-
<!-- Uncomment to add embedded tomcat service
<mbean code="org.jboss.tomcat.EmbeddedTomcatServiceSX"
- name="DefaultDomain:service=EmbeddedTomcat"/>
+ name="DefaultDomain:service=EmbeddedTomcat">
+ </mbean>
-->
<!--
@@ -377,6 +387,7 @@
|
| Besure to check that the configuration values are valid for your
| environment.
+ |
<mbean code="org.jboss.jetty.JettyService"
name=":service=Jetty">
<attribute name="JettyHome">../../jetty</attribute>
@@ -389,14 +400,50 @@
<!-- ==================================================================== -->
+ <!-- J2EE deployment -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.ejb.ContainerFactory"
+ name=":service=ContainerFactory">
+ <attribute name="VerifyDeployments">true</attribute>
+ <attribute name="ValidateDTDs">false</attribute>
+ <attribute name="MetricsEnabled">false</attribute>
+ <attribute name="VerifierVerbose">true</attribute>
+ <attribute name="BeanCacheJMSMonitoringEnabled">false</attribute>
+ </mbean>
+
+ <!-- Make sure you change EmbeddedTomcat to Jetty if you are using Jetty -->
+ <mbean code="org.jboss.deployment.J2eeDeployer"
+ name="J2EE:service=J2eeDeployer">
+ <attribute name="DeployerName">Default</attribute>
+ <attribute name="JarDeployerName">:service=ContainerFactory</attribute>
+ <attribute name="WarDeployerName">:service=EmbeddedTomcat</attribute>
+ </mbean>
+
+ <!--
+ | Uncomment this and disable previous J2eeDeployer
+ | entry to enable an alternative "scoped" deployment
+ |
+ <mbean code="org.jboss.deployment.scope.J2eeGlobalScopeDeployer"
+ name="J2EE:service=J2eeDeployer">
+ <attribute name="DeployerName">Default</attribute>
+ <attribute name="JarDeployerName">:service=ContainerFactory</attribute>
+ <attribute name="WarDeployerName">:service=EmbeddedTomcat</attribute>
+ </mbean>
+ -->
+
+
+ <!-- ==================================================================== -->
<!-- JBossMQ -->
<!-- ==================================================================== -->
<mbean code="org.jboss.mq.server.JBossMQService"
name="JBossMQ:service=Server"/>
- <!-- The StateManager is used to keep JMS perisitent state data. -->
- <!-- For example: what durable subscriptions are active. -->
+ <!--
+ | The StateManager is used to keep JMS perisitent state data.
+ | For example: what durable subscriptions are active.
+ -->
<mbean code="org.jboss.mq.server.StateManager"
name="JBossMQ:service=StateManager">
<attribute name="StateFile">jbossmq-state.xml</attribute>
@@ -408,7 +455,10 @@
<attribute name="DataDirectory">../../db/jbossmq/</attribute>
</mbean>
- <!-- InvocationLayers are the different transport methods that can be used to
access the server -->
+ <!--
+ | InvocationLayers are the different transport methods that can
+ | be used to access the server.
+ -->
<mbean code="org.jboss.mq.il.jvm.JVMServerILService"
name="JBossMQ:service=InvocationLayer,type=JVM">
<attribute name="ConnectionFactoryJNDIRef">java:/ConnectionFactory</attribute>
@@ -433,7 +483,11 @@
<attribute name="XAConnectionFactoryJNDIRef">UILXAConnectionFactory</attribute>
</mbean>
- <!-- The following three line create 3 topics named: testTopic, example, and bob
-->
+ <!--
+ | The following three line create 3 topics named:
+ |
+ | testTopic, example, bob
+ -->
<mbean code="org.jboss.mq.server.TopicManager"
name="JBossMQ:service=Topic,name=testTopic"/>
<mbean code="org.jboss.mq.server.TopicManager"
@@ -441,8 +495,11 @@
<mbean code="org.jboss.mq.server.TopicManager"
name="JBossMQ:service=Topic,name=bob"/>
- <!-- The following 9 line create 9 topics named: testQueue, controlQueue, A, B,
-->
- <!-- C, D, E, F, and ex -->
+ <!--
+ | The following 9 line create 9 topics named:
+ |
+ | testQueue, controlQueue, A, B, C, D, E, F, ex
+ -->
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=testQueue"/>
<mbean code="org.jboss.mq.server.QueueManager"
@@ -462,11 +519,7 @@
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=ex"/>
-
- <!-- ==================================================================== -->
- <!-- For Message Driven Beans -->
- <!-- ==================================================================== -->
-
+ <!-- The JMS provider loader -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name=":service=JMSProviderLoader,name=JBossMQProvider">
<attribute name="ProviderName">DefaultJMSProvider</attribute>
@@ -476,6 +529,8 @@
<attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
<attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
</mbean>
+
+ <!-- The server session pool for Message Driven Beans -->
<mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
name=":service=ServerSessionPoolMBean,name=StdJMSPool">
<attribute name="PoolName">StdJMSPool</attribute>
@@ -484,27 +539,6 @@
</attribute>
</mbean>
-
- <!-- Make sure you change EmbeddedTomcat to Jetty if you are using Jetty -->
- <mbean code="org.jboss.deployment.J2eeDeployer"
- name="J2EE:service=J2eeDeployer">
- <attribute name="DeployerName">Default</attribute>
- <attribute name="JarDeployerName">:service=ContainerFactory</attribute>
- <attribute name="WarDeployerName">:service=EmbeddedTomcat</attribute>
- </mbean>
-
- <!-- Uncomment this and disable previous J2eeDeployer
- entry to enable an alternative "scoped" deployment
- <mbean code="org.jboss.deployment.scope.J2eeGlobalScopeDeployer"
- name="J2EE:service=J2eeDeployer">
- <attribute name="DeployerName">Default</attribute>
- <attribute name="JarDeployerName">:service=ContainerFactory</attribute>
- <attribute name="WarDeployerName">:service=EmbeddedTomcat</attribute>
- </mbean>
- -->
-
-
-
<!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
<mbean code="org.jboss.resource.ConnectionFactoryLoader"
name="JCA:service=ConnectionFactoryLoader,name=JmsXA">
@@ -591,18 +625,20 @@
<!-- ==================================================================== -->
+ <!-- Monitoring and Management -->
+ <!-- ==================================================================== -->
+
<!-- Uncomment to enable JMX monitoring of the bean cache
<mbean code="org.jboss.monitor.BeanCacheMonitor"
name="Monitor:name=BeanCacheMonitor"/>
-->
- <!-- ==================================================================== -->
<!-- ==================================================================== -->
<!-- Scheduler Service -->
<!-- ==================================================================== -->
- <!-- Uncomment this to enable Scheduling - ->
+ <!-- Uncomment this to enable Scheduling
<mbean code="org.jboss.util.Scheduler" name=":service=Scheduler">
<constructor>
<arg type="java.lang.String" value=":server=Scheduler"/>
@@ -614,7 +650,7 @@
<arg type="long" value="-1"/>
</constructor>
</mbean>
- <!- - -->
+ -->
<!-- Uncomment this and set up according to manual to add Castor JDO service
<mbean code="org.jboss.jdo.castor.CastorJDOImpl"
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
