-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b164
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8178266 | 10 | Daniel Fuchs | P2 | Resolved | Fixed | b04 |
Analyzing this bug JCK-7308180, I encountered a tck-red-9 issue.
Tests failing in System.LoggerFinder ( getLocalizedLogger and getLogger) both methods state in the spec that an NPE will be thrown when “name” or “module” parameter is null.
However , when the module is limited to “java.base” and the java.logging is not present, the default implementation does not check for null-ability of “name” parameter.
Hence NPE is not thrown. (default Implementation)
Tests failing in System.LoggerFinder ( getLocalizedLogger and getLogger) both methods state in the spec that an NPE will be thrown when “name” or “module” parameter is null.
However , when the module is limited to “java.base” and the java.logging is not present, the default implementation does not check for null-ability of “name” parameter.
Hence NPE is not thrown. (default Implementation)
- backported by
-
JDK-8178266 System.LoggerFinder#getLogger or getLocalizedLogger does not throw NPE
-
- Resolved
-