JDK-6844054 : (bf) Eliminate dependency on javax.management.ObjectName
- Type: Bug
- Component: core-libs
- Sub-Component: java.nio
- Affected Version: 7
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2009-05-21
- Updated: 2014-10-10
- Resolved: 2009-07-17
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.
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 7 |
|---|
7 b64Fixed  |
Related Reports
|
Relates :
|
Description
The new management interface java.nio.BufferPoolMXBean results in an dependency on javax.management.ObjectName. This bug tracks eliminating the resulting dependency from the implementation. For example, java.nio.Bits and sun.nio.ch.FileChannelImpl can expose the details of the buffer pools and java.management.PlatformComponent can construct the BufferPoolMXBean. When the JDK is modularized then this would allow BufferPoolMXBean to be put into a management/jmx without a circularly dependency on a core or other module containing Buffers and FileChannel.
Comments
|