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 2010/01/07 11:43:56 UTC

[jira] Resolved: (SLING-1275) Return value of ComponentContext#locateContext should be checked for null value

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

Carsten Ziegeler resolved SLING-1275.
-------------------------------------

    Resolution: Fixed

I've checked the whole code base and added null checks where they were missing.

> Return value of ComponentContext#locateContext should be checked for null value
> -------------------------------------------------------------------------------
>
>                 Key: SLING-1275
>                 URL: https://issues.apache.org/jira/browse/SLING-1275
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons, Engine, Extensions, JCR, Servlets
>    Affects Versions: Servlets Post 2.0.4, JCR Resource 2.0.6, Engine 2.0.6, Commons Scheduler 2.2.0, Adapter 2.0.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Servlets Post 2.0.6, JCR Resource 2.0.8, Engine 2.1.0, Commons Scheduler 2.2.2, Adapter 2.0.6
>
>
> During binding of services using the ComponentContext#locateService method it might happen that this method returns null (although this is very rare) - However we should check against a null return value to prevent NPEs further down

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.