JDK-6355323 : Clarify how DescriptorKey used in an MBean interface should be handled
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-11-24
  • Updated: 2010-07-29
  • Resolved: 2006-04-14
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.
6 b81Fixed
Related Reports
Relates :  
Relates :  
Please refer to 6337679 for the context.

Basically, the javadoc should explicitely say the use of DescriptorKey for an MBean interface is considered only for that interface and not for its super interface, if any.

The javadoc might also say how DescriptorKey use within an MBean interface (on getter/setter/operation) is handled; Foo implements FooMBean and FooMBean extends Fooliest:
- if the annotated method is defined only in the MBean super interface (Fooliest), then DescriptorKey is considered,
- if the annotated method is defined both in interface and super interface, only the use in the interface is considered.

EVALUATION Clarify as stated. Until 6398884 is fixed, we will not specify explicitly what happens when a method is inherited from more than one parent interface and not overridden in a child interface.

EVALUATION Should say that interface annotations are only considered in the MBean or MXBean interface itself, not its parents. Should say that method annotations are considered in the most specific interface in which the method appears.