Adobe Global Community

Pages Tagged with 'Adobe Experience Manager'

Seattle Adobe Experience Manager Developer Community

Connecting the Adobe Experience Manager (AEM) Developer Community in the Seattle area for best practices, case studies, product launch demos, trends, events, social networking and dev tips and tricks.

/community/groups/seattle-adobe-experience-cloud-developer-community.html
Atlanta Adobe Experience Manager Developer Community

Connecting the Adobe Experience Manager (AEM) Developer Community in the Atlanta area for best practices, case studies, product launch/demos, trends, events, social networking and tips & tricks.

/community/groups/atlanta-adobe-experience-manager-meetup-group.html
How to Fix AEM Link Checker Issues with Broken Image Links

Users expect an engaging and quality experience on your site. If little things aren’t working correctly, they are likely to get frustrated and leave. Link Checker is a useful tool within AEM that validates all external and internal links on content pages. It shows all invalid, expired, and pre-dated links broken in the authoring environment

/learn/articles/2019/01/how-to-fix-aem-link-checker-issue-with-broken-image-links.html
How does Sling resolve an AEM Page to the correct resource type?

On the AEM forum there’s an interesting question: Does this mean that all requests to the page node are internally redirected to _jcr_content for HTML and XML calls but not for other extensions ? Without answering the question right here, it raises the question: How is a cq:Page node actually resolved? Or how does Sling know, that it should resolve a call to a cq:Page node to the resourcetype specified in its jcr:content node? Especially since the 'cq:Page' does not have a 'sling:resourceType' property at all?

/learn/articles/2019/01/how-does-sling-resolve-an-aem-page-to-the-correct-resource-type.html
Catching up with David Gonzalez

This year at Summit I didn’t have booth duty, which allowed me more freedom to browse the Community Pavilion and attend sessions and labs. One of the labs I was excited to attend was David Gonzalez’s (https://www.linkedin.com/in/davidjgonzalez/). David is a Technical Marketing Engineer at Adobe and co-project lead of ACS AEM Commons/Tools/Samples, and his lab was called “Accelerate Your Development with Experience Manager Core Components” (https://adobesummit.lanyonevents.com/2018/connect/sessionDetail.ww?SESSION_ID=6149). After his lab, David took some time to talk with me about what’s new with ACS AEM Commons. He mentioned 2 note really interesting items: Managed Controlled Processes (https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp/index.html) and Asset Share Commons (https://adobe-marketing-cloud.github.io/asset-share-commons/), which we hope to cover in a later article/podcast. He was even nice enough to setup our interview with Bryan Stopp, which you will be able to hear on this blog at a later date.

/learn/articles/2019/01/catching-up-with-david-gonzalez.html
Writing unit tests for AEM (part 2): Maven Setup

In the previous post I showed you how easy it is to start using SlingContext. If you start to use this approach in your own project and just copy the code, your Maven build is likely to fail with messages like this: [ERROR] testActivate_unconfiguredParams(de.joerghoh.cqdump.samples.unittest.ReplicationServletTest) Time elapsed: 0.01 s <<< ERROR! org.apache.sling.testing.mock.osgi.NoScrMetadataException: No OSGi SCR metadata found for class de.joerghoh.cqdump.samples.unittest.ReplicationServlet

/learn/articles/2019/01/writing-unit-tests-for-aem-part-2-maven-setup.html
Including Service Users in Your AEM Package

While working on a project recently, I needed to include a service user within the Adobe Experience Manager package I was deploying. By doing this, administrators wouldn’t have to create the service users manually During this process, I ran into a few exceptions and wanted to share.

/learn/articles/2019/01/including-service-users-in-your-aem-package.html
Mastering AEM Dispatcher Part 7: Securing the Dispatcher

The AEM Dispatcher is not just a caching engine and load balancer, is the first line of defense for your AEM application. That's why it's so important to ensure your Dispatcher is configured to be secure.

/learn/articles/2019/01/mastering-aem-dispatcher-part-7-securing-the-dispatcher.html
From SCR annotations to OSGI annotations

Since the beginning of AEM development we used annotations to declare OSGI services; @Component, @Service, @Property and @Reference should be known to everyone how has ever developed backend stuff for AEM. The implementation behind these annotations came from the Apache Felix project, and they were called the SCR annotations (SCR = Service Component Runtime). But unlike the Service Component Runtime, which is part of the OSGI standard for quite some, these annotations were not standardized. This changed with OSGI Release 6.

/learn/articles/2019/01/from-scr-annotations-to-osgi-annotations.html
OSGi: migration to OSGi annotations caveats

I think that every developer from AEM/Sling world has already read many articles regarding switching to the R6 and R7 OSGi annotations. But new annotations do not only allow us to write less boilerplate code, but also bring new caveats and we better be aware of them. Several days ago there was suggested a PR for AC Tool which fixes missing referenced service in AEM 6.4, even though this service was shown as satisfied in Web Console

/learn/articles/2019/01/migration-osgi-annotations-caveats-sling-aem.html