You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/03/30 13:12:53 UTC

[jira] [Resolved] (SLING-4510) Sling LogService could provide more usable output

     [ https://issues.apache.org/jira/browse/SLING-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-4510.
-------------------------------------
    Resolution: Fixed

Thanks for your patch, David. It's applied
In addition I changed from StringBuffer to StringBuilder

> Sling LogService could provide more usable output
> -------------------------------------------------
>
>                 Key: SLING-4510
>                 URL: https://issues.apache.org/jira/browse/SLING-4510
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Commons Log Service 1.0.2
>            Reporter: David Bosschaert
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: Commons Log Service 1.0.4
>
>         Attachments: SLING-4510.diff
>
>
> The Sling Log Service generates log messages when services change. However the information in those log messages could be improved. For example the following is a typical log message:
> {code}some.bsn Service [4242] ServiceEvent REGISTERED{code}
> It would be good to expand the log message to include the service's ObjectClass so that you know which service is actually being registered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)