Yes you can, for example via the resource-resolver.https://docs.adobe.com/docs/en/aem/6-1/ref/javadoc/org/apache/sling/api/resource/ResourceResolver.html
I would see if extra bindings here, would do the trick. Then you don't have to include it in every HTML-file.Example (slide 40+41) : https://adapt.to/content/dam/adaptto/production/presentations/2014/adaptTo2014-Lazy-AEM-developer-Sling-Models-Sightly-Feike-Visser.pdf/_jcr_content/renditions/origina...
Two things here:1. Try to avoid admin sessions if you can2. Since 6.0 there is a preferred way to get this, see this article for more details: http://stackoverflow.com/questions/35859278/aem-how-to-get-administrative-resource-resolver-since-getadministrativeresourc
In your example I don't see the point of the XComponent class.And in both cases I would start with directly using values in the component, like:${properties.jcr:title}Only if need to write logic, write code. Otherwise leave it in the component I would say.
Here a sample of your code in a project:https://github.com/heervisscher/htl-examples/blob/master/core/src/main/java/com/adobe/examples/htl/core/linkedlist/MiniNav.java
Looking at your bean on your HTL expressions, they don't match...you have .fPath and activeAttrand you have getFpath() and getActiveattr() <p>fpath : ${navlist.fPath}</p> <p>activeAttr: ${navlist.activeAttr}</p>
Employee
I would see if extra bindings here, would do the trick. Then you don't have to include it in every HTML-file.Example (slide 40+41) : https://adapt.to/content/dam/adaptto/production/presentations/2014/adaptTo2014-Lazy-AEM-developer-Sling-Models-Sightly-Feike-Visser.pdf/_jcr_content/renditions/origina...Questions
10/11/16
