commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Neidhart (JIRA)" <>
Subject [jira] [Updated] (LOGGING-95) [logging] extended API: getChildLogger(String)
Date Wed, 20 Feb 2013 09:15:12 GMT


Thomas Neidhart updated LOGGING-95:

    Fix Version/s: 2.0
> [logging] extended API: getChildLogger(String)
> ----------------------------------------------
>                 Key: LOGGING-95
>                 URL:
>             Project: Commons Logging
>          Issue Type: Improvement
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Jörg Hohwiller
>            Priority: Minor
>             Fix For: 2.0
>         Attachments: ASF.LICENSE.NOT.GRANTED--getChildLogger.diff,
> This is a feature request for the commons-logging API already discussed on the
> mailing list. The idea is to have an extended interface rather than Log that
> adds additional methods (getChildLogger and getName) that have already been
> requested for a long while. The suggested approach does not break compatibility
> of JCL. The existing Log interface is not touched and shall esp. not be
> deprecated. The new interface may only be used as needed but aims to prevent
> having even more additional logging APIs in future. The suggestion is to change
> the implementation in a way that all classes that implement Log shall implement
> Logger and fullfill the contract of the additional methods. In my request I
> still leave it open what happens to LogFactory but my suggestion is to leave it
> untouched (except for javadoc updates). Further I recomment to add an abstract
> class to the "impl" package that implements the Logger interface but does not
> implement any methods. The Logger interface may then recommend in its javadoc to 
> extend the abstract class rather than directly implementing the interface. This
> would allow to have less trouble if -however- in future an additional feature
> request for the Logger API arises.

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:

View raw message