User: mnf999
Date: 01/08/29 22:19:07
Added: src/etc/conf/default jboss-service.xml
Removed: src/etc/conf/default jboss.jcml
Log:
Just to make sure people know what file to use.
BTW jboss.jcml still works
Revision Changes Path
1.1 jboss/src/etc/conf/default/jboss-service.xml
Index: jboss-service.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- $Id: jboss-service.xml,v 1.1 2001/08/30 05:19:07 mnf999 Exp $ -->
<!--
| This is where you can add and configure your MBeans.
|
| *ATTENTION*
|
| The order of the listing here is the same order as
| the MBeans are loaded. Therefore if a MBean depends on another
| MBean to be loaded and started it has to be listed after all
| the MBeans it depends on.
-->
<server>
<!--
The Classpath element is needed for http based installations
we need to list all the archives that the server needs at boot
if the installation is local and the configuration is from file
then there is no need to list the files and it should commented
-->
<classpath archives="
castor.jar,
castor-jdo-plugin.jar,
com.mortbay.ftp.jar,
com.mortbay.jetty.jar,
com.mortbay.jetty.jmx.jar,
com.mortbay.jetty.sasl.jar,
com.mortbay.tools.jar,
concurrent.jar,
crimson.jar,
cryptix-sasl-jetty.jar,
gnu-regexp.jar,
hsql.jar,
hsql-plugin.jar,
jaas.jar,
JavaGroups.jar,
javax-sasl.jar,
jaxp.jar,
jbosscx.jar,
jbossha.jar,
jboss-j2ee.jar,
jboss.jar,
jbossmq.jar,
jbossmx.jar,
jbosspool.jar,
jbosssx.jar,
jcert.jar,
jetty-plugin.jar,
jmxtools.jar,
jndi.jar,
jnet.jar,
jnpserver.jar,
jpl-pattern.jar,
jpl-util.jar,
jsr77.jar,
jsse.jar,
jts.jar,
mail.jar,
org.apache.jasper.jar,
tyrex.jar,
tyrex-tm-plugin.jar,
xalan.jar"/>
<!-- ==================================================================== -->
<!-- Class Loading -->
<!-- ==================================================================== -->
<mbean code="org.jboss.web.WebService"
name="JBOSS-SYSTEM:service=Webserver">
<attribute name="Port">8083</attribute>
</mbean>
<!-- ==================================================================== -->
<!-- JNDI -->
<!-- ==================================================================== -->
<mbean code="org.jboss.naming.NamingService"
name="JBOSS-SYSTEM:service=Naming">
<attribute name="Port">1099</attribute>
</mbean>
<mbean code="org.jboss.naming.JNDIView"
name="JBOSS-SYSTEM:service=JNDIView"/>
<!-- ==================================================================== -->
<!-- Transactions -->
<!-- ==================================================================== -->
<mbean code="org.jboss.tm.TransactionManagerService"
name="JBOSS-SYSTEM:service=TransactionManager">
<attribute name="TransactionTimeout">300</attribute>
<!-- Use this attribute if you need to use a specific Xid
implementation
<attribute name="XidClassName">oracle.jdbc.xa.OracleXid</attribute>
-->
</mbean>
<!--
| 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="JBOSS-SYSTEM:service=TransactionManager">
<attribute name="ConfigFileName">../conf/default/domain.xml</attribute>
</mbean>
-->
<mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
name="JBOSS-SYSTEM:service=ClientUserTransaction">
</mbean>
<!-- ==================================================================== -->
<!-- Security -->
<!-- ==================================================================== -->
<!-- Uncomment to enable the sample SRPVerifierStore service
<mbean code="org.jboss.security.srp.SRPVerifierStoreService"
name="Security:name=SRPVerifierStoreService">
<attribute name="JndiName">SRPDefaultVerifierSource</attribute>
<attribute name="StoreFile">SRPVerifierStore.ser</attribute>
</mbean>
-->
<!-- Uncomment to enable the SRP login service
<mbean code="org.jboss.security.srp.SRPService"
name="service:name=SRPService">
<attribute name="JndiName">SRPServerInterface</attribute>
<attribute name="VerifierSourceJndiName">SRPDefaultVerifierSource</attribute>
<attribute name="AuthenticationCacheJndiName">SRPAuthenticationCache</attribute>
<attribute name="ServerPort">10099</attribute>
</mbean>
-->
<!-- JAAS security manager and realm mapping -->
<mbean code="org.jboss.security.plugins.JaasSecurityManagerService"
name="Security:name=JaasSecurityManager">
<attribute name="SecurityManagerClassName">
org.jboss.security.plugins.JaasSecurityManager
</attribute>
</mbean>
<!-- Uncomment to enable the XML implementation of the JAAS policy
<mbean code="org.jboss.security.plugins.SecurityPolicyService"
name="Security:name=SecurityPolicyService">
<attribute name="JndiName">DefaultSecurityPolicy</attribute>
<attribute name="PolicyFile">sample_policy.xml</attribute>
</mbean>
-->
<!-- ==================================================================== -->
<!-- JDBC - Initialize the databases -->
<!-- to ConnectionFactoryLoader -->
<!-- ==================================================================== -->
<mbean code="org.jboss.jdbc.JdbcProvider"
name="JBOSS-SYSTEM:service=JdbcProvider">
<attribute name="Drivers">
org.hsql.jdbcDriver
</attribute>
</mbean>
<mbean code="org.jboss.jdbc.HypersonicDatabase"
name="JBOSS-SYSTEM:service=Hypersonic">
<attribute name="Port">1476</attribute>
<attribute name="Silent">true</attribute>
<attribute name="Database">default</attribute>
<attribute name="Trace">false</attribute>
</mbean>
<!-- ==================================================================== -->
<!-- JBossCX setup, for J2EE connector architecture support -->
<!-- The RARDeployer and three Connection Manager Factories are parts of -->
<!-- JBoss and do not need further configuration. -->
<!-- ==================================================================== -->
<mbean code="org.jboss.resource.RARDeployer"
name="JCA:service=RARDeployer">
</mbean>
<!--
| 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>
<attribute name="FactoryClass">
org.jboss.pool.connector.jboss.MinervaNoTransCMFactory
</attribute>
<attribute name="Properties"></attribute>
</mbean>
<!--
| 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>
<attribute name="FactoryClass">
org.jboss.pool.connector.jboss.MinervaSharedLocalCMFactory
</attribute>
<attribute name="Properties"></attribute>
</mbean>
<!--
| 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>
<attribute name="FactoryClass">
org.jboss.pool.connector.jboss.MinervaXACMFactory
</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.
|
<mbean code="org.jboss.resource.ConnectionFactoryLoader"
name="JCA:service=ConnectionFactoryLoader,name=XAMinervaDS">
<attribute name="FactoryName">XAMinervaDS</attribute>
<attribute name="RARDeployerName">JCA:service=RARDeployer</attribute>
<attribute name="ResourceAdapterName">
Minerva JDBC XA Resource Adapter
</attribute>
<attribute name="Properties">
XADataSourceClass=YourXADataSourceClassNameHere
SomeOtherPropertySuchAsURL=url=urltomydatabase
</attribute>
<attribute name="ConnectionManagerFactoryName">
MinervaXACMFactory
</attribute>
<attribute name="ConnectionManagerProperties">
# Pool type - uncomment to force, otherwise it is the default
#PoolConfiguration=per-factory
# Connection pooling properties - see
# org.jboss.pool.PoolParameters
MinSize=0
MaxSize=10
Blocking=true
GCEnabled=false
IdleTimeoutEnabled=false
InvalidateOnError=false
TrackLastUsed=false
GCIntervalMillis=120000
GCMinIdleMillis=1200000
IdleTimeoutMillis=1800000
MaxIdleTimeoutPercent=1.0
</attribute>
<attribute name="PrincipalMappingClass">
org.jboss.resource.security.ManyToOnePrincipalMapping
</attribute>
<attribute name="PrincipalMappingProperties">
userName=sa
password=
</attribute>
</mbean>
-->
<!-- ==================================================================== -->
<!-- JDBC - showing the conversion of XADataSourceLoader -->
<!-- to ConnectionFactoryLoader -->
<!-- ==================================================================== -->
<!--
| XADataSourceLoader is now deprecated.
| It now converts to ConnectionFactoryLoader mbeans. See below for brief
| instructions.
|
<mbean code="org.jboss.jdbc.XADataSourceLoader"
name="JBOSS-SYSTEM:service=XADataSource,name=DefaultDS">
<attribute name="PoolName">DefaultDS</attribute>
<attribute
name="DataSourceClass">org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl</attribute>
<attribute name="Properties"></attribute>
<attribute name="URL">jdbc:HypersonicSQL:hsql://localhost:1476</attribute>
<attribute name="GCMinIdleTime">1200000</attribute>
<attribute name="JDBCUser">sa</attribute>
<attribute name="MaxSize">10</attribute>
<attribute name="Password" />
<attribute name="GCEnabled">false</attribute>
<attribute name="InvalidateOnError">false</attribute>
<attribute name="TimestampUsed">false</attribute>
<attribute name="Blocking">true</attribute>
<attribute name="GCInterval">120000</attribute>
<attribute name="IdleTimeout">1800000</attribute>
<attribute name="IdleTimeoutEnabled">false</attribute>
<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 code="org.jboss.resource.ConnectionFactoryLoader"
name="JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=DefaultDS">
<attribute
name="Properties">ConnectionURL=jdbc\:HypersonicSQL\:hsql\://localhost\:1476</attribute>
<attribute name="FactoryName">DefaultDS</attribute>
<attribute name="TransactionManagerName">java:/TransactionManager</attribute>
<attribute name="ResourceAdapterName">Minerva JDBC LocalTransaction
ResourceAdapter</attribute>
<attribute name="RARDeployerName">JCA:service=RARDeployer</attribute>
<attribute
name="ConnectionManagerFactoryName">MinervaSharedLocalCMFactory</attribute>
<attribute name="ConnectionManagerProperties">#
#Wed Aug 15 16:17:29 EDT 2001
InvalidateOnError=false
Blocking=true
IdleTimeoutMillis=1800000
MaxSize=10
TimestampUsed=false
IdleTimeoutEnabled=false
GCIntervalMillis=120000
MinSize=0
GCMinIdleMillis=1200000
GCEnabled=false
MaxIdleTimeoutPercent=1.0
</attribute>
<attribute name="PrincipalMappingClass">
org.jboss.resource.security.ManyToOnePrincipalMapping
</attribute>
<attribute name="PrincipalMappingProperties">userName=sa</attribute>
</mbean>
<!-- ==================================================================== -->
<!-- JBoss Server Management -->
<!-- ==================================================================== -->
<!-- AS Temporary not available
<mbean code="org.jboss.management.ServerDataCollector"
name="Management:service=Collector">
<attribute name="RefreshSleep">5000</attribute>
</mbean>
-->
<!-- ==================================================================== -->
<!-- Web Container -->
<!-- ==================================================================== -->
<!-- Uncomment to add embedded tomcat service
<mbean code="org.jboss.tomcat.EmbeddedTomcatServiceSX"
name="JBOSS-SYSTEM:service=EmbeddedTomcat">
</mbean>
-->
<!--
| Uncomment to enable the Jetty service.
|
| 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>
<attribute name="Configuration">jetty.xml</attribute>
<attribute name="WebDefault">../../jetty/etc/webdefault.xml</attribute>
<attribute name="UnpackWars">true</attribute>
<attribute name="PublishMBeans">true</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.
-->
<mbean code="org.jboss.mq.server.StateManager"
name="JBossMQ:service=StateManager">
<attribute name="StateFile">jbossmq-state.xml</attribute>
</mbean>
<!-- The PersistenceManager is used to store messages to disk. -->
<mbean code="org.jboss.mq.pm.file.PersistenceManager"
name="JBossMQ:service=PersistenceManager">
<attribute name="DataDirectory">db/jbossmq/</attribute>
</mbean>
<!--
| 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>
<attribute
name="XAConnectionFactoryJNDIRef">java:/XAConnectionFactory</attribute>
</mbean>
<mbean code="org.jboss.mq.il.rmi.RMIServerILService"
name="JBossMQ:service=InvocationLayer,type=RMI">
<attribute name="ConnectionFactoryJNDIRef">RMIConnectionFactory</attribute>
<attribute name="XAConnectionFactoryJNDIRef">RMIXAConnectionFactory</attribute>
</mbean>
<mbean code="org.jboss.mq.il.oil.OILServerILService"
name="JBossMQ:service=InvocationLayer,type=OIL">
<attribute name="ConnectionFactoryJNDIRef">ConnectionFactory</attribute>
<attribute name="XAConnectionFactoryJNDIRef">XAConnectionFactory</attribute>
</mbean>
<mbean code="org.jboss.mq.il.uil.UILServerILService"
name="JBossMQ:service=InvocationLayer,type=UIL">
<attribute name="ConnectionFactoryJNDIRef">UILConnectionFactory</attribute>
<attribute name="XAConnectionFactoryJNDIRef">UILXAConnectionFactory</attribute>
</mbean>
<!--
| 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"
name="JBossMQ:service=Topic,name=example"/>
<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, ex
-->
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=testQueue"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=controlQueue"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=A"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=B"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=C"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=D"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=E"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=F"/>
<mbean code="org.jboss.mq.server.QueueManager"
name="JBossMQ:service=Queue,name=ex"/>
<!-- The JMS provider loader -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name=":service=JMSProviderLoader,name=JBossMQProvider">
<attribute name="ProviderName">DefaultJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JBossMQProvider
</attribute>
<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>
<attribute name="PoolFactoryClass">
org.jboss.jms.asf.StdServerSessionPoolFactory
</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">
<attribute name="FactoryName">JmsXA</attribute>
<attribute name="RARDeployerName">JCA:service=RARDeployer</attribute>
<attribute name="ResourceAdapterName">JMS Adapter</attribute>
<attribute name="ConnectionManagerFactoryName">MinervaXACMFactory</attribute>
<!-- See the documentation for the specific connection manager
implementation you are using for the properties you can set -->
<attribute name="ConnectionManagerProperties">
# Pool type - uncomment to force, otherwise it is the default
#PoolConfiguration=per-factory
# Connection pooling properties - see
# org.jboss.pool.PoolParameters
MinSize=0
MaxSize=10
Blocking=true
GCEnabled=false
IdleTimeoutEnabled=false
InvalidateOnError=false
TrackLastUsed=false
GCIntervalMillis=120000
GCMinIdleMillis=1200000
IdleTimeoutMillis=1800000
MaxIdleTimeoutPercent=1.0
</attribute>
<!-- Principal mapping configuration -->
<attribute name="PrincipalMappingClass">
org.jboss.resource.security.ManyToOnePrincipalMapping
</attribute>
<attribute name="PrincipalMappingProperties">
</attribute>
</mbean>
<!-- ==================================================================== -->
<!-- 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>
-->
<!-- ==================================================================== -->
<!-- Auto deployment -->
<!-- ==================================================================== -->
<mbean code="org.jboss.deployment.AutoDeployer"
name="JBOSS-SYSTEM:service=AutoDeployer">
<attribute name="Deployers">
JCA:service=RARDeployer;
JBOSS-SYSTEM:service=ServiceDeployer;
J2EE:service=J2eeDeployer
</attribute>
<attribute name="URLs">
../deploy/lib,
../deploy
</attribute>
<attribute name="Timeout">
3000
</attribute>
</mbean>
<!-- ==================================================================== -->
<!-- JMX adaptors -->
<!-- ==================================================================== -->
<!-- Moved to a JSR format, look for adaptors.jsr in deploy/lib
<mbean code="org.jboss.jmx.server.JMXAdaptorService"
name="Adaptor:name=RMI"/>
<mbean code="org.jboss.jmx.server.RMIConnectorService"
name="Connector:name=RMI"/>
<mbean code="com.sun.jdmk.comm.HtmlAdaptorServer" name="Adaptor:name=html">
<attribute name="MaxActiveClientCount">10</attribute>
<attribute name="Parser" />
<attribute name="Port">8082</attribute>
</mbean>
-->
<!-- ==================================================================== -->
<!-- Mail Connection Factory -->
<!-- ==================================================================== -->
<!-- moved to a snippet format under deploy/lib
<mbean code="org.jboss.mail.MailService" name=":service=Mail">
<attribute name="JNDIName">Mail</attribute>
<attribute name="ConfigurationFile">mail.properties</attribute>
<attribute name="User">user_id</attribute>
<attribute name="Password">password</attribute>
</mbean>
-->
<!-- ==================================================================== -->
<!-- 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
<mbean code="org.jboss.util.Scheduler" name=":service=Scheduler">
<constructor>
<arg type="java.lang.String" value=":server=Scheduler"/>
<arg type="java.lang.String"
value="org.jboss.util.Scheduler$SchedulableExample"/>
<arg type="java.lang.String" value="Schedulabe Test,12345"/>
<arg type="java.lang.String" value="java.lang.String,int"/>
<arg type="long" value="0"/>
<arg type="long" value="10000"/>
<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"
name="JBOSS-SYSTEM:service=CastorJDO,name=someName">
<attribute name="Configuration">
file:../conf/default/database.xml
</attribute>
<attribute name="JndiName">jdo/someName</attribute>
<attribute name="LockTimeout">0</attribute>
<attribute name="LoggingEnabled">false</attribute>
<attribute name="CommonClassPath">false</attribute>
</mbean>
-->
<!-- ==================================================================== -->
<!-- Add your custom MBeans here -->
<!-- ==================================================================== -->
</server>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
