Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6745844

Minor fixes to MXBean-related specifications

    Details

      Description

      ###@###.### writes:
      "1. javax.management.openmbean.MXBeanMappingClass
      The spec for value says:

       This class must have a public constructor with a single argument of type Type.

      However I didn't find anywhere words about what happens if this is not true.
      Please note, that the specs for MXBeanMappingFactoryClass.value has similar words ("This class must have a public constructor with no arguments.") And in MXBean annotation's spec we find answer to the same question for MXBeanMappingFactoryClass:

       If the class does not have a no-argument constructor, or if calling the constructor produces an exception, then the MXBean is invalid and an attempt to register it in the MBean Server will produce a NotCompliantMBeanException.


      2. javax.management.JMX.newMBeanProxy(MBeanServerConnection,ObjectName,Class,MBeanOptions)
       
        If opts.isNotificationEmitter() is true, then ...

      But opts is of type MBeanOptions and that class does not have such method. Perhaps it's worth to add words like "If opts has method isNotificationEmitter() and this method returns true ..."


      3. javax.management.MBeanServerInvocationHandler(MBeanServerConnection,ObjectName,JMX.MBeanOptions)

      This new constructor has no javadoc which would be very welcome."

        Attachments

          Activity

            People

            • Assignee:
              sjiang Shanliang Jiang (Inactive)
              Reporter:
              emcmanus Eamonn McManus
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Imported:
                Indexed: