United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-6355323 : Clarify how DescriptorKey used in an MBean interface should be handled

Details
Type:
Bug
Submit Date:
2005-11-24
Status:
Closed
Updated Date:
2010-07-29
Project Name:
JDK
Resolved Date:
2006-04-14
Component:
core-svc
OS:
generic
Sub-Component:
javax.management
CPU:
generic
Priority:
P2
Resolution:
Fixed
Affected Versions:
6
Fixed Versions:

Related Reports
Relates:
Relates:

Sub Tasks

Description
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.

                                    

Comments
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.
                                     
2005-11-25
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.
                                     
2006-03-15



Hardware and Software, Engineered to Work Together