5.4. Configuring Legacy Core Services

The legacy core services specified in the $JBOSS_HOME/server/PROFILE/conf/jboss-service.xml file are started just after server starts up the microcontainer. The file contains MBeans for various services including logging, security, JNDI, JNDIView etc. If you commenting out a service, it is not loaded on startup.

Note

This file will be dropped as the services are converted to microcontainer Beans or MBeans that are deployed as deploy directory services.
Note that if an MBeans definition has nested comments, you need to comment out the MBean in two sections, leaving the original comment as it was.

Example 5.2. JNDIView MBean Commented out

<!-- Section 1 commented out
<mbean code="org.jboss.naming.JNDIView"
name="jboss:service=JNDIView"
xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">
-->
<!-- The HANamingService service name -->
<!-- Section two commented out
<attribute name="HANamingService">jboss:service=HAJNDI</attribute></mbean>
-->
If you then restart JBoss, you will see that the JNDIView service no longer appears in the JMX Management Console (JMX Console) listing. In practice, you should rarely, if ever, need to modify this file, though there is nothing to stop you adding extra MBean entries in here if you want to. The alternative is to use a separate file in the deploy directory, which allows your service to be hot deployable.