You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2007/08/05 23:21:29 UTC
[jira] Assigned: (OPENEJB-624) Extract Logger Categories to a
separate interface
[ https://issues.apache.org/jira/browse/OPENEJB-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins reassigned OPENEJB-624:
-------------------------------------
Assignee: karan singh malhi
> Extract Logger Categories to a separate interface
> -------------------------------------------------
>
> Key: OPENEJB-624
> URL: https://issues.apache.org/jira/browse/OPENEJB-624
> Project: OpenEJB
> Issue Type: Improvement
> Components: general
> Reporter: karan singh malhi
> Assignee: karan singh malhi
> Priority: Minor
> Fix For: 3.0
>
> Attachments: openejb-624.patch
>
>
> If the logger names could be extracted to constants in an interface,
> then it will be easier to make changes to logger names and will also
> lead to lesser errors , because logger names are case sensitive
> So for example, instead of obtaining a logger like
> public static final Logger logger =
> Logger.getInstance("OpenEJB.startup",
> Assembler.class.getPackage().getName());
> We could do something like
> public static final Logger logger =
> Logger.getInstance(LogCategory.OPENEJB_STARTUP,
> Assembler.class.getPackage().getName());
> In fact, with static import it will just be
> public static final Logger logger =
> Logger.getInstance(OPENEJB_STARTUP,
> Assembler.class.getPackage().getName());
> LogCategory would contain the names of all loggers used in openejb.
> Since there are just a few loggers, they could be defined within the
> Logger class itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.