[
http://issues.ops4j.org/jira/browse/PAXLOGGING-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11339
]
Niclas Hedhman commented on PAXLOGGING-15:
------------------------------------------
I don't understand this fix nor the problem. PaxLoggingService returns a
PaxLogger with the Bundle in it, and should be possible to always pass Bundle
info along.
Also, the spec allows the Bundle in the LogEvent to be null, if not
associated... Let's discuss this when we meet next time. Meanwhile I will
re-open the issue, so I don't forget it.
> OSGi TCK test failure: LogEntry instances have null bundle fields
> -----------------------------------------------------------------
>
> Key: PAXLOGGING-15
> URL: http://issues.ops4j.org/jira/browse/PAXLOGGING-15
> Project: Pax Logging
> Issue Type: Bug
> Affects Versions: 0.9.7
> Reporter: Stuart McCulloch
> Assignee: Stuart McCulloch
> Fix For: 1.0
>
>
> Most of the LogEntry events generated by Pax-Logging have null bundle fields,
> because the calling bundle is not provided in the LogService API. To fill in
> the bundle field we need to implement the ServiceFactory interface and supply
> a customized instance for each bundle that basically delegates to the
> underlying Pax-Logging service instance.
--
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
