[
https://issues.apache.org/jira/browse/SLING-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481188#comment-13481188
]
Felix Meschberger commented on SLING-2626:
------------------------------------------
I think it is not clearly specified what happens if the path is given as null.
Looking at the JavaDoc of the getResource(Resource, String) method, though, I
would assume that it is considered an error situation if the path is null.
Hence I would prefer throwing an Exception instead of just returning null.
On the other hand, we could be lenient return null (as proposed) assuming a
resource without a path just does not exist and we return this as such.
> NPE in ResourceResolverImpl.getResource
> ---------------------------------------
>
> Key: SLING-2626
> URL: https://issues.apache.org/jira/browse/SLING-2626
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Affects Versions: JCR Resource 2.1.0, Resource Resolver 1.0.0
> Reporter: Radu Cotescu
> Assignee: Carsten Ziegeler
> Labels: patch
> Fix For: Resource Resolver 1.0.0
>
> Attachments: sling_rev_1400664.patch
>
>
> The path parameter is not checked for null in either of the
> ResourceResolverImpl.getResource(String path) and
> ResourceResolverImpl.getResource(Resource base, String path), which makes the
> two methods throw NPE on several lines.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
