[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-581) Seam logging does not report correct line number/class name/method name under Log4J or JDK1.4 logging

Gavin King (JIRA) jira-events at jboss.com
Fri Dec 15 21:28:05 EST 2006


     [ http://jira.jboss.com/jira/browse/JBSEAM-581?page=all ]

Gavin King closed JBSEAM-581.
-----------------------------

    Resolution: Done

OK, I took inspiration from your patch, but I ended up ripping out clogging entirely. Thanks.

> Seam logging does not report correct line number/class name/method name under Log4J or JDK1.4 logging
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-581
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-581
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0.CR2
>         Environment: Java 1.5.0_06
> Windows XP Pro
> Tomcat 6.0.0
>            Reporter: Mike Quilleash
>         Assigned To: Gavin King
>             Fix For: 1.1.1.GA
>
>         Attachments: Log4JLogger.java, LogImpl.java, SeamLogFactory.java
>
>
> Seam uses a wrapper around commons logging to allow it to evaluate EL expressions as part of the log string.  However this adds an extra level to the call stack which the commons logging library is unaware of so the reporting of line numbers/class name/method name in log output always reports the line number in the Seam logging implementation rather than the calling code above it.
> This affects Log4J (line numbers/class name/method name) and JDK1.4 logging (class name/method name).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list