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/08/10 14:52:46 UTC

[jira] [Assigned] (SLING-4939) ServletResolver implementation is too verbose

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

Carsten Ziegeler reassigned SLING-4939:
---------------------------------------

    Assignee: Carsten Ziegeler

> ServletResolver implementation is too verbose
> ---------------------------------------------
>
>                 Key: SLING-4939
>                 URL: https://issues.apache.org/jira/browse/SLING-4939
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Servlets Resolver 2.3.8
>
>
> The servlet resolver implementation logs a lot of message in info level which are not really relevant, like when a provider is registered or a servlet is found which has not the required properties. These are all normal situations and partially covered at other places and logged, like the service registry.
> We can reduce the volume of log output if we change at least some messages to debug



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