[ http://jira.jboss.com/jira/browse/JBAS-3589?page=all ] David Gecawich updated JBAS-3589: --------------------------------- Description: Documentation incorrectly says that the JNDIView service is started (and disabled) from jboss-service.xml. Namely, JBoss AS 4.0.4. Getting Started Guide, 2.2.1 Core Services, page 8, says "if you have a look at this file [conf/jndi-service.xml], you'll see MBeans for various services including.... the JNDIView service service that we saw earlier. Try commenting out the entry for the JNDIView service..." PROBLEM: You cannot comment out the MBean entry for the JNDIView service in conf/jndi-service.xml because the MBean entry for the JNDIView service does not exist in the conf/jndi-service.xml file. The documentation appears to be incorrect. TO REPRODUCE: 1. Download the JBoss AS 4.0.4 Getting Started Guide. The links to the PDF and HTML files are below. PDF: http://labs.jboss.com/portal/jbossas/docs HTML: http://docs.jboss.org/jbossas/getting_started/v4/html/tour.html#d0e412 2. Install JBoss AS 4.0.4 as specified in the documentation (I installed the Full J2EE server profile) 3. Follow the instructions in Getting Started Guide, 2.2.1 Core Services, page 8 and open conf/jndi-service.xml in an editor. 4. Look for JNDIView in conf/jndi-service.xml Results: you cannot find JNDIView in conf/jndi-service.xml and cannot complete the example. Notes: 1. I searched jira.jboss.org on "JNDIView" and "naming-service.xml" and from the headers of items listed, did not see any apparent duplicate items. 2. We are upgrading from JBoss 3.2.5. In JBOss 3.2.5, JNDIView was present the in core jboss-service.xml configuration file. This service appears to have changed in JBoss 4.0.4, at least under some configurations, and the documentation may not have been updated to reflect this change. 3. I did some digging, and found that in JBoss 4.0.4, the MBean definition for "JNDIView" is included in the default configuration from the deploy file deploy/naming-service.xml (Iverify the JNDIView is loaded from the deploy/naming-service.xml file in the workaround). In JMX Console, JNDIView is loaded and can be invoked so the service is operational. 4. Since JNDIView is used as the example to describe how core services work in JBOss (a key concept) and how to disable a service, it is confusing to the reader why a core service is not in the jboss-service.xml and what the recommended procedure is to disable a core service in 4.0.4. Also, can one assume that JNDIView is no longer a core service? Possible Solution: Perhaps the JBoss AS 4.0.4 Getting Started doc can be updated to use another service that is loaded and disabled as an example, and a clarification can be made regarding JNDIView in section 2.2.1 to correct the example. Workaround: I found you can disable the JNDIView service as follows: 1. Goto JMX Console at http://localhost:8080/jmx-console/, find the JNDIView service to verify it is loaded. 2. Edit the /deploy/naming-service.xml file. 3. Comment out the MBean entry for JNDIView in this file, as follows: <!-- <mbean code="org.jboss.naming.JNDIView" name="jboss:service=JNDIView" xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml"> </mbean> --> 3. Restart JBoss. 4. Goto JMX Console at http://localhost:8080/jmx-console/, try to find the JNDIView service. You should not be able to find it, thus verifying that you successfully did not start the JNDIView service. was: Example incorrectly says JNDIView started from jboss-service.xml JBoss AS 4.0.4. Getting Started Guide, 2.2.1 Core Services, page 8, says "if you have a look at this file [conf/jndi-service.xml], you'ee MBeans for various sevrices including.... the JNDIView service service that we saw earlier. Try commenting out the entry for the JNDIView service..." PROBLEM: You cannot comment out the MBean entry for the JNDIView service in conf/jndi-service.xml because the MBean entry for the JNDIView service does not exist in the conf/jndi-service.xml file. The documentation appears to be incorrect. TO REPRODUCE: 1. Download the JBoss AS 4.0.4 Getting Started Guide. The links to the PDF and HTML files are below. PDF: http://labs.jboss.com/portal/jbossas/docs HTML: http://docs.jboss.org/jbossas/getting_started/v4/html/tour.html#d0e412 2. Install JBoss AS 4.0.4 as specified in the documentation (I installed the Full J2EE server profile) 3. Follow the instructions in Getting Started Guide, 2.2.1 Core Services, page 8 and open conf/jndi-service.xml in an editor. 4. Look for JNDIView in conf/jndi-service.xml Results: you cannot find JNDIView in conf/jndi-service.xml and cannot complete the example. Notes: 1. I searched jira.jboss.org on "JNDIView" and "naming-service.xml" and from the headers of items listed, did not see any apparent duplicate items. 2. We are upgrading from JBoss 3.2.5. In JBOss 3.2.5, JNDIView was present the in core jboss-service.xml configuration file. This service appears to have changed in JBoss 4.0.4, at least under some configurations, and the documentation may not have been updated to reflect this change. 3. I did some digging, and found that in JBoss 4.0.4, the MBean definition for "JNDIView" is included in the default configuration from the deploy file deploy/naming-service.xml (Iverify the JNDIView is loaded from the deploy/naming-service.xml file in the workaround). In JMX Console, JNDIView is loaded and can be invoked so the service is operational. 4. Since JNDIView is used as the example to describe how core services work in JBOss (a key concept) and how to disable a service, it is confusing to the reader why a core service is not in the jboss-service.xml and what the recommended procedure is to disable a core service in 4.0.4. Also, can one assume that JNDIView is no longer a core service? Possible Solution: Perhaps the JBoss AS 4.0.4 Getting Started doc can be updated to use another service that is loaded and disabled as an example, and a clarification can be made regarding JNDIView in section 2.2.1 to correct the example. Workaround: I found you can disable the JNDIView service as follows: 1. Goto JMX Console at http://localhost:8080/jmx-console/, find the JNDIView service to verify it is loaded. 2. Edit the /deploy/naming-service.xml file. 3. Comment out the MBean entry for JNDIView in this file, as follows: <!-- <mbean code="org.jboss.naming.JNDIView" name="jboss:service=JNDIView" xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml"> </mbean> --> 3. Restart JBoss. 4. Goto JMX Console at http://localhost:8080/jmx-console/, try to find the JNDIView service. You should not be able to find it, thus verifying that you successfully did not start the JNDIView service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira