[jira] [Commented] (SLING-9487) Default for org.apache.sling.commons.log.file only set via metatype breaking the logstatus webconsole.

["Dominik Süß (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119469#comment-17119469 ] 

Dominik Süß commented on SLING-9487:
------------------------------------

PR at https://github.com/apache/sling-org-apache-sling-commons-log/pull/6

> Default for org.apache.sling.commons.log.file only set via metatype breaking the logstatus webconsole.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-9487
>                 URL: https://issues.apache.org/jira/browse/SLING-9487
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>            Reporter: Dominik Süß
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> As the default for {{org.apache.sling.commons.log.file}}  for PID {{org.apache.sling.commons.log.LogManager.factory.config}} is only set for the metatype the default only applies on setting the configuration via UI. 
> The webconsole UI is dependent on this path to be configured to group the loggers accordin to those writers and spawns a nullpointerexception if a config is getting registered (e.g. via sling installer or feature model) that doesn't set this parameter.
> The proposed solution to this bug is to make sure that configuration being registered without this path pick up the same default value defined as in the metatype. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)