JDK-4796780 : MLetContent class should be public
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-12-20
  • Updated: 2017-05-16
  • Resolved: 2005-02-19
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 b25Fixed
Related Reports
Relates :  
JDK-5072268 - Suggested API changes for JMX 2.0
Description
One of the changes specified for JMX 1.2 was that the MLet.check
method should be made protected so it could be overridden in
subclasses of MLet.  This is bug 4619509, also 4716826 ("Implement
VERSION tag in MLet").  A necessary part of this fix was that
the MLetContent class needed to be made public.

The consequence of this bug is that the JMX API is inconsistent, in
that a publicly-visible method references a non-visible class.  Though
the documentation says you can override this method, in practice you
can't.  The change is rendered useless by this problem.  Also, the
specification is inconsistent with the Change Log for the 1.2 MR,
which says the class is public.

This also leaves us in an awkward position as regards independent
implementors, who will be obliged to add an unspecified MLetContent
class to their implementations in order to be signature compatible.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang
01-09-2004
PUBLIC COMMENTS JMX 1.2 change log says MLetContent class should be public but it is not. This makes the API inconsistent, because a publicly-visible method MLet.check references this not-puhlicly-visible class.
01-09-2004
EVALUATION This implies an incompatible API change. So in theory this will only be possible either with a MR of JMX (1.3), or J2SE 1.6. ###@###.### 2003-03-05 MR of the JMX API is not possible because of required compatibility with J2EE 1.4. So committing for Mustang. ###@###.### 2004-02-10
05-03-2003