Interface Descriptor

Additional metadata for a JMX element. A Descriptor is associated with a MBeanInfo, MBeanAttributeInfo, etc. It consists of a collection of fields. A field is a name and an associated value.

Field names are not case-sensitive. The names descriptorType, descriptortype, and DESCRIPTORTYPE are all equivalent. However, the case that was used when the field was first set is preserved in the result of the getFields() and getFieldNames() methods.

Not all field names and values are predefined. New fields can be defined and added by any program.

A descriptor can be mutable or immutable. An immutable descriptor, once created, never changes. The Descriptor methods that could modify the contents of the descriptor will throw an exception for an immutable descriptor. Immutable descriptors are usually instances of ImmutableDescriptor or a subclass. Mutable descriptors are usually instances of DescriptorSupport or a subclass.

Certain fields are used by the JMX implementation. This means either that the presence of the field may change the behavior of the JMX API or that the field may be set in descriptors returned by the JMX API. These fields appear in italics in the table below, and each one has a corresponding constant in the JMX class. For example, the field defaultValue is represented by the constant JMX.DEFAULT_VALUE_FIELD.

Certain other fields have conventional meanings described in the table below but they are not required to be understood or set by the JMX implementation.

Field names defined by the JMX specification in this and all future versions will never contain a period (.). Users can safely create their own fields by including a period in the name and be sure that these names will not collide with any future version of the JMX API. It is recommended to follow the Java package naming convention to avoid collisions between field names from different origins. For example, a field created by example.com might have the name com.example.interestLevel.

Note that the values in the defaultValue, legalValues, maxValue, and minValue fields should be consistent with the type returned by the getType() method for the associated MBeanAttributeInfo or MBeanParameterInfo. For MXBeans, this means that they should be of the mapped Java type, called opendata(J) in the MXBean type mapping rules.

Some additional fields are defined by Model MBeans. See the information for ModelMBeanInfo, ModelMBeanAttributeInfo, ModelMBeanConstructorInfo, ModelMBeanNotificationInfo, and ModelMBeanOperationInfo, as well as the chapter "Model MBeans" of the JMX Specification. The following table summarizes these fields. Note that when the Type in this table is Number, a String that is the decimal representation of a Long can also be used.

Nothing prevents the use of these fields in MBeans that are not Model MBeans. The displayName, severity, and visibility fields are of interest outside Model MBeans, for example. But only Model MBeans have a predefined behavior for these fields.