Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 16
-
Component/s: security-libs
-
Subcomponent:
-
Resolved In Build:b03
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8250080 | 15.0.2 | Weijun Wang | P3 | Resolved | Fixed | b01 |
JDK-8250378 | 15.0.1 | Weijun Wang | P3 | Resolved | Fixed | b03 |
JDK-8247962 | 15 | Weijun Wang | P3 | Resolved | Fixed | b29 |
JDK-8280805 | 13.0.11 | Yuri Nesterenko | P3 | Resolved | Fixed | b01 |
Description
In XMLDsig, logging is in log4j style. For example:
LOG.debug("Register Resolver: {}: {}", javaClass, description);
but the implementation uses Java Logger style, which requires a position number inside "{}".
LOG.debug("Register Resolver: {}: {}", javaClass, description);
but the implementation uses Java Logger style, which requires a position number inside "{}".
Attachments
Issue Links
- backported by
-
JDK-8247962 XMLDsig logging does not work
-
- Resolved
-
-
JDK-8250080 XMLDsig logging does not work
-
- Resolved
-
-
JDK-8250378 XMLDsig logging does not work
-
- Resolved
-
-
JDK-8280805 XMLDsig logging does not work
-
- Resolved
-
- relates to
-
JDK-8280947 Adapt test/jdk/javax/xml/crypto/dsig/LogParameters.java for 13u
-
- Resolved
-
-
JDK-8247964 All log0() in com/sun/org/slf4j/internal/Logger.java should be private
-
- Closed
-
-
JDK-8254267 javax/xml/crypto/dsig/LogParameters.java failed with "RuntimeException: Unexpected log output:"
-
- Resolved
-
(2 relates to, 2 links to)