You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Thomas Watson (Jira)" <ji...@apache.org> on 2019/08/21 21:50:00 UTC
[jira] [Commented] (FELIX-6173) Enhance log message for events
[ https://issues.apache.org/jira/browse/FELIX-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912712#comment-16912712 ]
Thomas Watson commented on FELIX-6173:
--------------------------------------
I don't think this is spec compliant with https://osgi.org/specification/osgi.cmpn/7.0.0/service.log.html#d0e2883 which makes it clear that "Events.Bundle" logger name must be used. See https://osgi.org/members/bugzilla/show_bug.cgi?id=3071 for what is being proposed for R8.
Basically:
loggerName := legacyMapping '.' bsn
legacyMapping := Events.Bundle | Events.Framework | Events.Service | LogService
> Enhance log message for events
> ------------------------------
>
> Key: FELIX-6173
> URL: https://issues.apache.org/jira/browse/FELIX-6173
> Project: Felix
> Issue Type: Improvement
> Components: Log Service
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: log-1.2.2
>
>
> When a framework, bundle or service event is received, the logger name is currently hard-coded. We could improve the logging by using the bundle symbolic name instead.
> In addition for start level events it would be nice to also log the start level
--
This message was sent by Atlassian Jira
(v8.3.2#803003)