Bug 846628 - Use of non-standard log names should be changed or documented
Use of non-standard log names should be changed or documented
Status: NEW
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal (Show other bugs)
5.2.1.GA
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Default User
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-08 05:55 EDT by Martin Weiler
Modified: 2014-07-24 23:18 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Enhancement
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
List of several classes with non-standard log names (10.62 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2012-08-08 07:29 EDT, Clay
no flags Details

  None (edit)
Description Martin Weiler 2012-08-08 05:55:04 EDT
Description of problem:
There are several non-standard log names that are not documented. For example, in the PortalApplication class, the logger is defined as:
    protected static Log log = 
                     ExoLogger.getLogger("portal:PortalApplication");
instead of something more standard such as:
    protected static Log log = 
                     ExoLogger.getLogger(PortalApplication.class);

These non-standard log names should be changed to the standard naming conventions, or documented somewhere so that developers are able to use logging effectively.
Comment 1 Clay 2012-08-08 07:29:14 EDT
Created attachment 602999 [details]
List of several classes with non-standard log names

Note You need to log in before you can comment on or make changes to this bug.