[
http://issues.ops4j.org/browse/PAXLOGGING-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643#action_12643
]
Niclas Hedhman commented on PAXLOGGING-54:
------------------------------------------
This has been a known issue from the start, as it is very expensive to try to
locate the Bundle from where the call to the API class happens.
I will look into this again, to see if I can find a not so expensive solution.
Suggestions are welcome...
> Wrong log event source if we use the LogReaderService.
> ------------------------------------------------------
>
> Key: PAXLOGGING-54
> URL: http://issues.ops4j.org/browse/PAXLOGGING-54
> Project: Pax Logging
> Issue Type: Bug
> Affects Versions: 1.3.0
> Environment: win32, JDK1.6, Eclipse 3.3
> Reporter: Frank K.
> Assignee: Niclas Hedhman
>
> All log entries which was logged to commons.logging and collected form the
> LogReaderService have the wrong event source. All events have the same
> source the org.ops4j.pax.logging.pax-logging-api bundle.
--
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
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
