[
https://issues.apache.org/jira/browse/SLING-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2714.
-------------------------------------
Resolution: Fixed
Fix Version/s: Resource Resolver 1.0.4
Good catch - thanks for the patch, I've applied a slightly modified version
> Wrap LOGGER.debug calls in ResourceProviderEntry
> ------------------------------------------------
>
> Key: SLING-2714
> URL: https://issues.apache.org/jira/browse/SLING-2714
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.0.2
> Reporter: Alexander Muthmann
> Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.0.4
>
> Attachments: SLING-2714.diff
>
>
> In ResourceProviderEntry.java there are multiple LOGGER.debug calls which
> access Arrays.toString(). This causes the Arrays.toString() call to be
> executed no matter which Logger-Level is set.
> Those calls should be wrapped in a LOGGER.isDebugEnabled().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
