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

2008-02-05 Thread Carsten Ziegeler (JIRA)

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

Carsten Ziegeler updated SLING-220:
---

Remaining Estimate: 0h
 Original Estimate: 0h

I've committed a potential fix for this NPE, although I'm not sure if this is 
the right solution. At least the NPE is not occuring anymore.

> 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
>   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.



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

2008-02-05 Thread Felix Meschberger (JIRA)

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

Felix Meschberger updated SLING-220:


Description: 
When requesting a certain resource (e.g. 
http://localhost:5002//content/test/contacts.navimage.jpg) a 
NullPointerException may be thrown by the 
JcrResourceResolver.getResourceInternal method when trying to go back up the 
ResourceProviderEntry tree.

Stacktrace:

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)
  ...


  was:
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)
  ...



Updating issue description.

> 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
>
> When requesting a certain resource (e.g. 
> http://localhost:5002//content/test/contacts.navimage.jpg) a 
> NullPointerException may be thrown by the 
> JcrResourceResolver.getResourceInternal method when trying to go back up the 
> ResourceProviderEntry tree.
> Stacktrace:
> 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.