You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2015/02/02 12:38:34 UTC
[jira] [Resolved] (SLING-4376) ResourceResolver-mock throws
NullPointerException in resolve when absPath = null
[ https://issues.apache.org/jira/browse/SLING-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert resolved SLING-4376.
-----------------------------------
Resolution: Fixed
Fix Version/s: Testing ResourceResolver Mock 1.1.4
Completed: At revision: 1656443
problem is fixed in 1.1.3-SNAPSHOT
> ResourceResolver-mock throws NullPointerException in resolve when absPath = null
> --------------------------------------------------------------------------------
>
> Key: SLING-4376
> URL: https://issues.apache.org/jira/browse/SLING-4376
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing ResourceResolver Mock 1.1.2
> Reporter: Steven Walters
> Assignee: Stefan Seifert
> Labels: test
> Fix For: Testing ResourceResolver Mock 1.1.4
>
>
> According to the ResolverResolver API for the resolve function:
> {quote}
> absPath The absolute path to be resolved to a resource. If this
> * parameter is <code>null</code>, it is assumed to address the
> * root of the resource tree. If the path is relative it is
> * assumed relative to the root, that is a slash is prepended to
> * the path before resolving it.
> {quote}
> However, in the MockResourceResolver, this scenario is not actually handled and instead throws a {{NullPointerException}} when attempting to look for indexes of the characters {{?}} or {{#}} in the path string
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)