[jira] [Resolved] (SLING-2040) Avoid logger instantiation and extra servlet resolver null check in RequestData

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler resolved SLING-2040.
-------------------------------------

    Resolution: Fixed

Fixed in revision 1086978

> Avoid logger instantiation and extra servlet resolver null check in RequestData
> -------------------------------------------------------------------------------
>
>                 Key: SLING-2040
>                 URL: https://issues.apache.org/jira/browse/SLING-2040
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.2.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: Engine 2.2.4
>
>
> The RequesgData object only uses a logger if the servlet resolver is null - however RequestData objects are only created if a servlet resolver is available
> Therefore we could avoid this extra null check and logging and  therefore the logger instantiation
> To avoid a potential race condition, we pass the checked servlet resolver to the request data object

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira