JDK-6369229 : For several methods, the javadoc body comes from the ancestor in place of from the interface
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-01-05
  • Updated: 2022-01-25
  • Resolved: 2006-04-01
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 b79Fixed
Related Reports
Relates :  
Relates :  
Description
While verifying the 6273662, I saw that the body of the description of methods
ImmutableDescriptor.equals()
ImmutableDescriptor.hashCode()
modelmbean.DescriptorSupport.hashCode()
modelmbean.DescriptorSupport.equals()
is wrong.
It is copied from class Object as what we expect is to get it copied from interface Descriptor.
Strangely, if you use the javadoc tool that comes with J2SE 1.4, you get the expected description.
A full scan might help to dig out other occurrences.

Comments
SUGGESTED FIX Ideally a fixed javadoc (see 6376959) should be enough and we wouldn't have to do anything on JMX side. If that scenario is unlikely to happen, then we should modify the javadoc of methods ImmutableDescriptor.equals() ImmutableDescriptor.hashCode() modelmbean.DescriptorSupport.hashCode() modelmbean.DescriptorSupport.equals() to copy what comes from Descriptor interface. By doing so we duplicate a comment for nothing but getting a relevant javadoc !
14-03-2006

EVALUATION This must be fixed. The JMX API is erroneous as of now.
14-03-2006