[
http://issues.ops4j.org/jira/browse/PAXLOGGING-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11008
]
Stuart McCulloch commented on PAXLOGGING-19:
--------------------------------------------
Are you sure? I thought r10011 only changed the .iml file... and the
handleEvents still seem to be missing from PaxLoggerImpl.
> Legacy log API calls generate Event Admin events only for trace
> ---------------------------------------------------------------
>
> Key: PAXLOGGING-19
> URL: http://issues.ops4j.org/jira/browse/PAXLOGGING-19
> Project: Pax Logging
> Issue Type: Bug
> Reporter: Damian Golda
> Assignee: Niclas Hedhman
>
> I have application with lot of 3rd party libraries using slf4j and log4j api.
> I' d like to use LogReaderService and intercept logs and then analyze them.
> But unfortunately it doesn't work.
> I found that PaxLoggerImpl (used by
> org.ops4j.pax.logging.slf4j.Slf4jLogger) calls
> m_service.handleEvents(m_bundle, null, LogService.LOG_DEBUG,
> message, t );
> only in trace method. And of course I need it in debug and info...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/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
