You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Woonsan Ko (JIRA)" <ji...@apache.org> on 2011/07/22 22:46:57 UTC
[jira] [Created] (CXF-3680) Logging locations are hidden with
Slf4jLogger and Log4jLogger
Logging locations are hidden with Slf4jLogger and Log4jLogger
-------------------------------------------------------------
Key: CXF-3680
URL: https://issues.apache.org/jira/browse/CXF-3680
Project: CXF
Issue Type: Improvement
Affects Versions: 2.3.5, 2.4.1
Reporter: Woonsan Ko
Priority: Minor
Fix For: 2.3.6, 2.4.2
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3680) Logging locations are hidden with
Slf4jLogger
Posted by "Woonsan Ko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Woonsan Ko updated CXF-3680:
----------------------------
Attachment: CXF-3680-patch.diff
Attaching patch for 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
>
> Attachments: CXF-3680-patch.diff
>
>
> 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
[jira] [Resolved] (CXF-3680) Logging locations are hidden with
Slf4jLogger
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-3680.
------------------------------
Resolution: Fixed
> 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
> Assignee: Daniel Kulp
> Priority: Minor
> Fix For: 2.3.6, 2.4.2, 2.5
>
> Attachments: CXF-3680-patch.diff
>
>
> 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
[jira] [Assigned] (CXF-3680) Logging locations are hidden with
Slf4jLogger
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-3680:
--------------------------------
Assignee: Daniel Kulp
> 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
> Assignee: Daniel Kulp
> Priority: Minor
> Fix For: 2.3.6, 2.4.2, 2.5
>
> Attachments: CXF-3680-patch.diff
>
>
> 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
[jira] [Updated] (CXF-3680) Logging locations are hidden with
Slf4jLogger
Posted by "Woonsan Ko (JIRA)" <ji...@apache.org>.
[ 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