[DERBY-5007] Implement an alternative error-logging mechanism using the java.util.logging idiom.

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: JDBC
• Labels: derby_triage10_11
• Urgency: Normal
• Issue & fix info: Newcomer
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 07/Feb/11 15:08
• Updated: 17/Jun/21 02:07

Description

The Driver.getParentLogger() method introduced by JDBC 4.1 gives applications a way to hook into the error-logging mechanism used by the database--provided that the database does its logging via a java.util.logging.Logger. It would be good to support this idiom in Derby alongside the existing home-grown error logger. If we implement this support, then we can remove the extra dummy driver classes added by the derby-4869-24-ab-getParentLogger.diff patch as part of DERBY-4869. Those classes exist only to support the vacuous implementations of Driver.getParentLogger() which raise unimplemented-feature exceptions.

Issue Links

• duplicates: DERBY-3481 Take advantage of java.util.logging functionality for non-J2ME platforms.
• is related to: DERBY-6350 Provide a rolling file implementation of derby.log