Answer this AEM question 💡
If the model deals with content prefer RESOURCE class , if request specific logic is required then use SlinghttpServletrequest. Clarity of use is required when including both in the model
Shubham Gupta’s Post
More Relevant Posts
-
Struggling to bring composable methodologies to your organization? According to #MACH Alliance's research, "9 out of 10 decision-makers say composable technology will be instrumental to their organization’s success in the next five years." But getting there can be a challenge. 🤓 That's why we're excited to partner with VShift on their #AEM Digital Experience Accelerator that: -Increases flexibility -Boosts speed to market -And lowers cost Learn more: https://lnkd.in/ednN_AjB
Build AEM experiences faster, with less dependence on specialized resources. See how: https://lnkd.in/eQp2xXva
-
-
AEM Notes💡 All about Sling models in AEM✅ #aem hashtag #aemdeveloper hashtag #aemarchitect hashtag #adobeexperiencemanager
-
AEM Notes💡 All about Sling models in AEM✅ #aem #aemdeveloper #aemarchitect #adobeexperiencemanager
-
Junior Front End Developer @ Concordia University | Freelance Marketing Specialist & Content Creator
One of the things that is always difficult is writing queries for AEM. You may spend several minutes to hours constructing some complex ones. In fact, the documentation for query commands available are out there but are often hidden within a Stack Overflow article or on a GitHub repo with not many stars. It is important though before writing commands to understand how the JCR infrastructure works, which should lead you into understanding what the commands do and how they function. My major takeaway from three years working on AEM so far is that it is a large database where everything can be searched (pages, tags, files) and you can search node within node for some neat yet complex queries. I leave you with my faves I use all the time in XPATH: JCR:like -> find exact match for property and text you provide it JCR:contains -> works to find anything within an array of strings or nodes, maybe with multiple tags XS:DateTime -> extremely useful when comparing times And the last one is more of a technique, but nesting. After you make a command inside of square brackets, you can add another //* after it to look within that particular node. this means you can go several levels deep! There is still a ton to discover and a lot to learn and many unknowns. Enjoy the journey! 🎉
-
🚀 Check out my latest blog post! 🚀 🌟Event Listener Essentials in AEM: A Comprehensive Guide🌟 In this blog article, I'll provide an overview of Event Listeners in AEM, explain how they work, and offer instructions on how to use them correctly. If you're interested in AEM or are an AEM developer, you'll find this blog informative and useful. Check it out here: 👉https://lnkd.in/gf2sFgip I'd love to hear your thoughts and feedback! Feel free to leave a comment or reach out directly. #aemdeveloper #aemcommunity #aemcoral #adobe #adobeaemdeveloper #OSGI #eventListener #java #community #AEM #AdobeExperienceManager #EventListeners #WebDevelopment #DigitalExperience #TechBlog #Adobe #ContentManagement #WebDevelopmentTips
-
Check out my new blog post about an AEM misconfiguration vulnerability that helped me get my first Hall of Fame. Special thanks to Fat Selimi Story of a Simple AEM Misconfiguration Bug : https://lnkd.in/gYaT9VfY
Story of a Simple AEM Misconfiguration Bug
abhishek-praveen.github.io
It depends on your use case. If your business logic only requires you to deal with the current resouce, then Resource.class makes sense. But if you want to use some request attributes, request values in your sling model. As well as for sling model exporter where the call does not goes to component html, and it is entirely based on mapping of your resourceType and sling model. In this case SlingHttpRequest.class is beneficial and required.