You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2022/04/05 15:18:00 UTC

[jira] [Closed] (SLING-11182) Correct potential errors introduced by BVP logging

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

Radu Cotescu closed SLING-11182.
--------------------------------

> Correct potential errors introduced by BVP logging
> --------------------------------------------------
>
>                 Key: SLING-11182
>                 URL: https://issues.apache.org/jira/browse/SLING-11182
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Core 2.4.4
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting Core 2.4.6
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> SLING-11122 has the potential to introduce some NPEs in applications using an older version of the Sling API but a newer version of the Scripting Core bundle. The logging functionality introduced relies on the presence of the {{RequestProgressTracker}}. However, older versions of the Sling API didn't annotate {{org.apache.sling.api.SlingHttpServletRequest#getRequestProgressTracker}} with {{@NotNull}}.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)