Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Sat, 23 Jul 2011 03:01:10 +0000 (UTC)
From: "Woonsan Ko (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: 
 <1783002288.704.1311390070790.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <10589430.15590.1311367617861.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CXF-3680) Logging locations are hidden with
 Slf4jLogger
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Woonsan Ko updated CXF-3680:
----------------------------

      Description: 
The current CXF Slf4jLogger just invokes the internal slf4j logger object. 
In this way, it cannot show the original logging location.
For example, when logging configuration contains something like '%C:%L', it 
prints the Slf4jLogger class name and its line number instead of the caller's class name and its line number.
In order to show the original logging locations nicely, we can use LocationAwareLogger#log(, fqcn, ...) operation. With provision of the FQCN of the wrapper class, the underlying slf4j logger will find the exact logging location.

I'll provide a patch for this in this issue.

  was:
The current CXF Slf4jLogger and Log4jLogger just invokes the internal logger object. 
In this way, it cannot show the original logging location.
For example, when logging configuration contains something like '%C:%L', it 
prints the Slf4jLogger/Log4jLogger class name and its line number instead of the caller's class name and its line number.
In order to show the original logging locations nicely, we can use LocationAwareLogger#log(, fqcn, ...) operation. With provision of the FQCN of the wrapper class (Slf4jLogger or Log4jLogger, in this case), the underlying slf4j or log4j
logger will find the exact logging location.

I'll provide a patch for this in this issue.

    Fix Version/s: 2.5
          Summary: Logging locations are hidden with Slf4jLogger  (was: Logging locations are hidden with Slf4jLogger and Log4jLogger)

Log4jLogger already used location-aware logging operation. This problem happens only with Slf4jLogger.

> Logging locations are hidden with Slf4jLogger
> ---------------------------------------------
>
>                 Key: CXF-3680
>                 URL: https://issues.apache.org/jira/browse/CXF-3680
>             Project: CXF
>          Issue Type: Improvement
>    Affects Versions: 2.4.1, 2.3.5
>            Reporter: Woonsan Ko
>            Priority: Minor
>             Fix For: 2.3.6, 2.4.2, 2.5
>
>
> The current CXF Slf4jLogger just invokes the internal slf4j logger object. 
> In this way, it cannot show the original logging location.
> For example, when logging configuration contains something like '%C:%L', it 
> prints the Slf4jLogger class name and its line number instead of the caller's class name and its line number.
> In order to show the original logging locations nicely, we can use LocationAwareLogger#log(, fqcn, ...) operation. With provision of the FQCN of the wrapper class, the underlying slf4j logger will find the exact logging location.
> I'll provide a patch for this in this issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira