You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/02/05 19:34:08 UTC

[jira] Resolved: (SLING-220) NPE when requesting content with selector

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

Felix Meschberger resolved SLING-220.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

Fixed in Rev. 618734 by refactoring resource resolution using the ResourceProviderTree. Instead of finding the longest prefix matching ResourceProvider and going back up following the parent links, I added a ResourceProviderEntry.getResource(String) method, which walks down the tree looking for the longest matching prefix and asking each resource provider going back up in turn for the resource.

This way, we do not have to manage any parent provider links and may cleanly encapsulate the inner workings of the ResourceProviderEntry tree.

Please close this bug, if it fixes your issue. Thanks.



> NPE when requesting content with selector
> -----------------------------------------
>
>                 Key: SLING-220
>                 URL: https://issues.apache.org/jira/browse/SLING-220
>             Project: Sling
>          Issue Type: Bug
>          Components: Resource
>            Reporter: Tobias Bocanegra
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> request to:  http://localhost:5002//content/test/contacts.navimage.jpg
> java.lang.NullPointerException
>    at org.apache.sling.jcr.resource.internal.JcrResourceResolver.getResourceInternal(JcrResourceResolver.java:360)
>    at org.apache.sling.jcr.resource.internal.JcrResourceResolver.getResource(JcrResourceResolver.java:137)
>    at org.apache.sling.servlet.resolver.SlingServletResolver.getServletAt(SlingServletResolver.java:322)
>    at org.apache.sling.servlet.resolver.SlingServletResolver.resolveServlet(SlingServletResolver.java:145)
>   ...

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