Is there any change in behaviour of ResourceResolver(org.apache.sling.api.resource) in AEM 6.2 because it returns me NonExistingResource when trying to resolve resource(node) under /etc/xxx.
This used to work fine in AEM 6.0 SP3.
For example, We have few data pages under /etc/lists/top-navigation-configuration-page which we(anonymous users in publish) were able to resolve in WCMUse classes in AEM 6.0 SP3 using getResourceResolver.resolve("etc/lists/top-navigation-configuration-page"). But this piece of code is returning NonExistingResource in AEM 6.2. However, using service resource resolver(resolverFactory.getServiceResourceResolver(param)), resources under /etc/xxx are resolved.
Thanks in advance
Solved! Go to Solution.
The approach you have mentioned i.e. service resource resolver(in AEM 6.2) is a replacement for admin resource resolver(in AEM 6.0), but the issue i reported is about resource resolver implicit object in AEM component jsp or WCMUse class unable to resolve resources under /etc/*** even the cloud service configurations.
In AEM 6.0 SP3, we were able to resolve without admin resource resolver.
Thanks for the information. Anonymous user do not have read permissions in AEM 6.2 but available in AEM 6.0.
Workaround is to get service resource resolver and resolve resources under /etc/xxx