You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2022/09/28 09:43:00 UTC
[jira] [Closed] (SLING-11367) Potential NPE as ResolveContext.getProviderState() is nullable
[ https://issues.apache.org/jira/browse/SLING-11367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joerg Hoh closed SLING-11367.
-----------------------------
> Potential NPE as ResolveContext.getProviderState() is nullable
> ---------------------------------------------------------------
>
> Key: SLING-11367
> URL: https://issues.apache.org/jira/browse/SLING-11367
> Project: Sling
> Issue Type: Sub-task
> Components: JCR
> Affects Versions: JCR Resource 3.2.0
> Reporter: Angela Schreiber
> Assignee: Angela Schreiber
> Priority: Minor
> Fix For: JCR Resource 3.2.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> since {{ResolveContext.getProviderState()}} is defined to return a nullable provider state code analysis spots this a potential source for NPE. according to [~cziegeler] this should never return null as long as the provider is active.
> i would suggest to move access to session, resourcefactory and helperdata to a utility with comments on why the NPE should not occur.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)