db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-5007) Implement an alternative error-logging mechanism using the java.util.logging idiom.
Date Mon, 07 Feb 2011 15:09:30 GMT
Implement an alternative error-logging mechanism using the java.util.logging idiom.
-----------------------------------------------------------------------------------

                 Key: DERBY-5007
                 URL: https://issues.apache.org/jira/browse/DERBY-5007
             Project: Derby
          Issue Type: Improvement
          Components: JDBC
            Reporter: Rick Hillegas


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.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message