United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6320104 Add ability to set to UNKNOWN the OperationInfo impact of an Open MBean and an MXBean
JDK-6320104 : Add ability to set to UNKNOWN the OperationInfo impact of an Open MBean and an MXBean

Details
Type:
Enhancement
Submit Date:
2005-09-06
Status:
Closed
Updated Date:
2010-07-29
Project Name:
JDK
Resolved Date:
2005-12-21
Component:
core-svc
OS:
generic
Sub-Component:
javax.management
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
6
Fixed Versions:

Related Reports
Relates:

Sub Tasks

Description
When you create a standard MBean, the operation impact is by default UNKNOWN; but if you create an MXBean with the same interface, the same operation will have an ACTION_INFO impact.
It would be clearer to have symmetry here, by using UNKNOWN.

                                    

Comments
EVALUATION

There are two ways to fix this.  Either allow OpenMBeanOperationInfoSupport to accept UNKNOWN as a possible impact value, which seems logical; or change the MXBean infrastructure so that it never generates an OpenMBeanOperationInfo but always a plain MBeanOperationInfo.  If the latter then we should probably just drop the creation of any OpenMBean*Info in MXBeans.  The main disadvantage of that is that it reduces the information available to Tiger clients who can't access the OpenType information that is available in the Descriptor of MBean*Info on Mustang.

I think it would be better to allow UNKNOWN as a value for OpenMBeanOperationInfoSupport.  So long as we're not deprecating the OpenMBean*Info classes, the omission of UNKNOWN seems gratuitous.
                                     
2005-09-06



Hardware and Software, Engineered to Work Together