db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3481) Take advantage of java.util.logging functionality for non-J2ME platforms.
Date Thu, 28 Feb 2008 22:55:54 GMT
Take advantage of java.util.logging functionality for non-J2ME platforms.
-------------------------------------------------------------------------

                 Key: DERBY-3481
                 URL: https://issues.apache.org/jira/browse/DERBY-3481
             Project: Derby
          Issue Type: Improvement
          Components: Services
            Reporter: Daniel John Debrunner
            Priority: Minor


The ability to expose Derby's logging through java.util.logging has many benefits due to the
standard nature of the jvm's logging including facilities such as rotating log files.

A set of logical operations on InfoStreams that mirrored a sub-set of  java.util.logging.Logger
would provide benefits such as dynamic changing the level of the log information, including
through standard JMX platform MBeans allowing other code to add handlers to Derby's logging
etc.

E.g. warning(), info(), config(), throwing() with the latter replacing the functionality of
ErrorStringBuilder.

Note that java.util.logging is not supported on J2ME/CDC/Foundation thus there would need
to be two InfoStreams implementations, one that forwarded calls to java.util.logging and one
that works as current.

Ideal project for incremental development, add a single method (e.g. config) and adapt a few
logging calls to that as a first step and then proceed to add more functionality.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message