[
http://issues.ops4j.org/browse/PAXLOGGING-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12248#action_12248
]
George Jordanoff commented on PAXLOGGING-32:
--------------------------------------------
I am posting a patch (FixedThreePaxLoggingBugs.patch) resolving the 3 bugs I
reported on the 27/Feb/09 09:59 AM (see the previous post).
These 3 resolved bugs (see patch in the File Attachments section of this page)
are :
1. As you can see here only when log via log4j API there is no information
about class name, method name, line number (all other API's have that
information)
2. As you can see only when log via Java Logging API the information about
class name, method name, line number is wrong : my class is
org.test.pax.logging.all.Activator (all other API's except log4J and Java
Logging API have correct information)
3. As you can see I log with 7 different levels in the Java Logging API
(SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) and only the first 3
levels are received (SEVERE, WARNING, INFO) the rest are lost - (all other
API's delivered all log messages, including debug messages)
> Wrong methodname and linenumber in combination with java.util.logging
> ---------------------------------------------------------------------
>
> Key: PAXLOGGING-32
> URL: http://issues.ops4j.org/browse/PAXLOGGING-32
> Project: Pax Logging
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Florian
> Assignee: Niclas Hedhman
> Attachments: FixedThreePaxLoggingBugs.patch, ReportBugs.zip
>
>
> Using a conversion-pattern for log4j like this
> log4j.appender.stdout.layout.ConversionPattern=%d{HH:mm:ss} %-5p [%-35c{1} -
> %-25M:%-4L] - %m%n
> and the standard logging framework for java "java.util.logging" the parameter
> "M" for methodname and "L" for linenumber are not correctly resolved. It
> seems that the classes are resolved one step too high in the stacktrace.
> This effect is the same whe using the (upper-case) "C" parameter for
> resolving full qualified class names. Lower-case "c" parameter is resolved
> correctly.
> I've attached a test bundle which demonstrates this behaviour and also
> outputs the expected results. However, for my experience, every bundle using
> java.util.logging struggles upon this problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
