User: chirino
Date: 01/09/12 19:39:50
Added: jbossmq/etc/conf/default core-service.xml jboss-service.xml
Removed: jbossmq/etc/conf/default jboss.jcml
Log:
Adjusted build and changed where the examples are placed in the final
distribution. The jboss-mq module should now build again and produce
the standalone jbossmq binary.
Revision Changes Path
1.1 build/jbossmq/etc/conf/default/core-service.xml
Index: core-service.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- $Id: core-service.xml,v 1.1 2001/09/13 02:39:50 chirino 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>
<!-- ==================================================================== -->
<!-- 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"/>
<!-- ==================================================================== -->
<!-- Add your custom MBeans here -->
<!-- ==================================================================== -->
</server>
1.1 build/jbossmq/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/09/13 02:39:50 chirino 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="
concurrent.jar,
gnu-regexp.jar,
JavaGroups.jar,
jboss-j2ee.jar,
jboss.jar,
jmxtools.jar,
jndi.jar,
jnpserver.jar,
"/>
<!-- ==================================================================== -->
<!-- Auto deployment -->
<!-- ==================================================================== -->
<mbean code="org.jboss.deployment.AutoDeployer"
name="JBOSS-SYSTEM:service=AutoDeployer">
<attribute name="Deployers">
JBOSS-SYSTEM:service=ServiceDeployer;
</attribute>
<attribute name="URLs">
../deploy/lib,
../deploy
</attribute>
<attribute name="Timeout">
3000
</attribute>
</mbean>
</server>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
