You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by santiagozky <gi...@git.apache.org> on 2015/03/13 16:29:59 UTC
[GitHub] sling pull request: SLING-4500: make sure that root has a primary ...
GitHub user santiagozky opened a pull request:
https://github.com/apache/sling/pull/72
SLING-4500: make sure that root has a primary type
when using the mock resource resolver, the root node does not have a primary type. this causes issues on some cases, for example:
Resource root= resourceResolver.getResource("/");
assertFalse(root.isResourceType("app/resourceType"));
will throw a null pointer exception.
I've added jcr:root as the primary type of the root node and a test case for this.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/santiagozky/sling bug/root-primary-type
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/72.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #72
----
commit 5eb786449c4389c8ad3d96ea0566443e7acc926c
Author: santiago garcia pimentel <sa...@netcentric.biz>
Date: 2015-03-13T15:21:59Z
make sure that root has a primary type
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] sling pull request: SLING-4500: make sure that root has a primary ...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/sling/pull/72
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---