Access Properties values set via WCM USE class
wrote...
Hi ptK,
Firstly, WCMUse[1] is deprecated, use WCMUsePojo[2] instead. Secondly, is there any particular reason you're using a ModifiableValueMap[3] to READ values? You should really just be using a regular ValueMap[4] instead, if you can help it.
In the event that you can't help but use the ModifiableValueMap, you may need to utilize a Service Resolver[5] that has sufficient privileges to read and write content, in lieu of the user's (possibly unprivileged) ResourceResolver[6].
[1] https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/com/adobe/cq/sightly/WCMUse.html
[2] https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/com/adobe/cq/sightly/WCMUsePojo.html
[3] https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/org/apache/sling/api/resource/ModifiableV...
[4] https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/org/apache/sling/api/resource/ValueMap.ht...
[5] https://helpx.adobe.com/experience-manager/using/querying-experience-manager-sling.html
[6] https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/org/apache/sling/api/resource/ResourceRes...
Tried Creating a resource from Service , but still facing the same issue.
// Method to create resource // resourcePath= getResource().getPath(); Values passed from WCM Class Map<String, Object> param = new HashMap<String, Object>(); param.put(ResourceResolverFactory.SUBSERVICE, "backendMap"); ResourceResolver resolver = null; try { resolver = resourceResolverFactory.getServiceResourceResolver(param); resolver.getResource(resourcePath); session = resolver.adaptTo(Session.class); } catch (org.apache.sling.api.resource.LoginException e1) { log.info("Login Exception "+e1.getMessage()); } return resolver.getResource(resourcePath);
When I view my "resource" object in my debugger I see all custom properties stored in WCM Class.
But when I try to access values using ${properties.key1fromResource} I see empty values
wrote...
wrote...
Hi ptK,
Firstly, WCMUse[1] is deprecated, use WCMUsePojo[2] instead. Secondly, is there any particular reason you're using a ModifiableValueMap[3] to READ values? You should really just be using a regular ValueMap[4] instead, if you can help it.
In the event that you can't help but use the ModifiableValueMap, you may need to utilize a Service Resolver[5] that has sufficient privileges to read and write content, in lieu of the user's (possibly unprivileged) ResourceResolver[6].
[1] https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/com/adobe/cq/sightly/WCMUse.html
[2] https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/com/adobe/cq/sightly/WCMUsePojo.html
[3] https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/org/apache/sling/api/resource/ModifiableV...
[4] https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/org/apache/sling/api/resource/ValueMap.ht...
[5] https://helpx.adobe.com/experience-manager/using/querying-experience-manager-sling.html
[6] https://docs.adobe.com/docs/en/aem/6-2/develop/ref/javadoc/org/apache/sling/api/resource/ResourceRes...
Tried Creating a resource from Service , but still facing the same issue.
// Method to create resource// resourcePath= getResource().getPath(); Values passed from WCM ClassMap<String, Object> param = new HashMap<String, Object>();param.put(ResourceResolverFactory.SUBSERVICE, "backendMap");ResourceResolver resolver = null;try {resolver = resourceResolverFactory.getServiceResourceResolver(param);resolver.getResource(resourcePath);session = resolver.adaptTo(Session.class);} catch (org.apache.sling.api.resource.LoginException e1) {log.info("Login Exception "+e1.getMessage());}return resolver.getResource(resourcePath);
When I view my "resource" object in my debugger I see all custom properties stored in WCM Class.
But when I try to access values using ${properties.key1fromResource} I see empty values
You're probably seeing the values in the debugger because it's showing you what has been modified during that session (without regard to whether you've saved your changes or not). However, without persisting your changes to the resource, when accessed via ${ properties.* } from your component, it's likely that your injected property key/values will be empty. There could also be a conflict because you're using a reserved/pre-defined "properties" variable, that just may not care about your injected values. I really don't know in this case, just throwing it out there as a possibility.
The easiest solution would probably be what Feike was suggesting, which is to utilize the ${ properties } variable for authored properties, and your own separate custom map variable for injected properties. Could also look into possibly using a @SlingFilter[1] (example[2]) instead of a WCMUsePojo class, to intercept the resource property definition and inject your values there. Should warn you that if you don't scope this properly, it could be resource heavy.
[1] https://sling.apache.org/documentation/the-sling-engine/filters.html
[2] https://github.com/Adobe-Consulting-Services/acs-aem-samples/blob/master/bundle/src/main/java/com/ad...
Related Conversations
