JDK-6320104 : Add ability to set to UNKNOWN the OperationInfo impact of an Open MBean and an MXBean
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-09-06
  • Updated: 2017-05-16
  • Resolved: 2005-12-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b63Fixed
Related Reports
Relates :  
JDK-6362002 - OpenMBeanOperationInfoSupport javadoc is contradictory about UNKNOWN impact
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.
06-09-2005