[jira] [Closed] (DERBY-3481) Take advantage of java.util.logging functionality for non-J2ME platforms.

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen closed DERBY-3481.
-------------------------------------

    Resolution: Duplicate

DERBY-5007 talks about adding support for java.util.logging using hooks introduced in JDBC 4.1.

I'm closing this issue and leaving DERBY-5007 open for further discussion.
                
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira