JDK-8145686 : SimpleConsoleLogger and LogRecord should take advantage of StackWalker to skip classes implementing System.Logger
- Type: Enhancement
- Component: core-libs
- Sub-Component: java.util.logging
- Affected Version: 9
- Priority: P4
- Status: Closed
- Resolution: Fixed
- Submitted: 2015-12-17
- Updated: 2016-08-24
- Resolved: 2015-12-21
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 9 |
|---|
9 b99Fixed  |
Related Reports
|
Duplicate :
|
|
|
Duplicate :
|
Description
When looking for the calling method to display in log files, the new StackWalking API makes it possible to implement filtering not only on the declaring class name, but also on the declaring class itself. SimpleConsoleLogger and LogRecord should take advantage of that to filter out classes implementing System.Logger. This will make it possible to easily implement logger wrappers without having to resort to using logp to preserve the calling class name and method name information.