Java Management Extensions

Errata for Java Management Extensions

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page 6
Example 1-2

public class GenericResource { //class details should be: public class GenericResource implements GenericResourceMBean { //class details

Anonymous   
Printed
Page 12
Figure 1.5

Top row of Figure 1.5 should read: OpenMBeanParameterInfo <implements> OpenMBeanParameterInfoSupport <subclasses> MBeanParameterInfo AUTHOR: The reader is correct. Figure 1-5 is wrong. The figure mistakenly depicts "OpenMBeanParameterInfoSupport implements OpenMBeanInfo and extends OpenMBeanInfo". The figure should depict "OpenMBeanParameterInfoSupport implements OpenMBeanParameterInfo and extends MBeanParameterInfo". Figure 5-1 is also incorrect. It mistakenly depicts "OpenMBeanParameterInfoSupport implements OpenMBeanParameterInfo and extends OpenMBeanInfo".

Anonymous   
Printed
Page 23
last paragraph

For each type of MBean, there is a Windows batch file and a Unix (Korn shell) script that builds and runs the code for that instrumentation strategy. The name of the script or batch file matches the instrumentation strategy: for example, the build script for dynamic MBeans is called dynamic.sh, and the batch file for building the source code for the version of the application instrumented as dynamic MBeans is called dynamic.bat. The major differences between the application versions are in the source code. The console output and the management view will show very little difference (other than output from the Ant build script) between the versions of the application. Should be: For each type of MBean, there is a Windows batch file that builds and runs the code. The name of the batch file matches the instrumentation strategy: the batch file for building the source code for the version of the application instrumented as dynamic MBeans is called dynamic.bat. The major differences between the application versions are in the source code. The console output and the management view will show very little difference (other than output from the Ant build script) between the versions of the application.

Anonymous   
Printed
Page 24
2nd to last line

<!-- Build the "standard" target --> should be: <!-- Build the "build-standard" target -->

Anonymous   
Printed
Page 77
4th paragrah, starts with "Five essential properties"

The description of the name property for the MBeanOperationInfo class starts with "The name of the constructor" while it should start with "The name of the operation". The same applies in general for the description and signature properties as well.

Anonymous   
Printed
Page 188
code below last paragraph

Object qmbean = null; try { Object mbean = mbeanServer.instantiate(qmbeanClassName); } catch {ReflectionException e) { //... } catch (MBeanException e) { //... } should be: Object qmbean = null; try { mbean = mbeanServer.instantiate(qmbeanClassName); } catch {ReflectionException e) { //... } catch (MBeanException e) { //... }

Anonymous