Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

koenve
koenve
Offline

Badges

Badges
15

Accepted Solutions

Accepted Solutions
3

Likes Received

Likes Received
14

Posts

Posts
15

Discussions

Discussions
2

Questions

Questions
13

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by koenve
Customize the badges you want to showcase on your profile
Re: Rollout Feature and AEM Experience Fragments - Adobe Experience Manager 13-06-2021
We were looking into the same and ended up creating a ticket with Adobe Support. Here’s their feedback:The ability to Create Live Copy has been added to AEMaaCS (via internal improvement request CQ-4268610). This was not backported to AEM 6.5 versions with the following feedback: If the improvement to create a live copy of a single experience fragment as source is backported, it does not allow creating structures as live copies. This means for every single XF in the language master, the user wou...

Views

481

Like

1

Replies

0
Re: Generate JSON response of an AEM Page - Adobe Experience Manager 07-05-2021
Hey! I think what you're looking for is the Sling Model Exporter. With it, you can define a Sling Model with the properties you want to expose, that is then available by browsing to your-page.model.json.

Views

267

Like

1

Replies

0
Re: What could cause a ReferenceError ContextHub is not d... - Adobe Experience Manager 15-04-2021
Hey! The AEM project archetype creates a page component for you when initialising your project. That page is including the contexthub code in your page. If you’re not using contexthub (and you’re not planning to use it either) you’re safe to remove it from your code. You should find something back under your page component in “customheaderlibs.html”: If you remove this line, the error shouldn’t appear anymore.Hope this helps!Koen

Views

315

Like

1

Replies

0
Re: JCR_OAK AemContext throws exceptions when trying to l... - Adobe Experience Manager 07-04-2021
Unfortunately, as we're using a JCR Query (via Session), we need a JCR_OAK AemContext.

Views

254

Likes

0

Replies

0
JCR_OAK AemContext throws exceptions when trying to load content - Adobe Experience Manager 03-04-2021
I’m trying to write a unit test for one of my services that does a query as part of the service. As such, I need a JCR_OAK AemContext to be able to test these changes. My unit test roughly looks like below: @ExtendWith(AemContextExtension.class) class MyUnitTest { private static final String PATH = "/content/we-retail/language-masters/en"; // need an OAK context to be able to do queries final AemContext CTX = new AemContext(ResourceResolverType.JCR_OAK); @BeforeEach public void init() { CTX.load...

Views

281

Likes

0

Replies

2
Re: Junit5 Mockito for Acitvate method - Adobe Experience Manager 26-03-2021
Nice, that's amazing. I'll check it out for myself too. Thanks!

Views

339

Likes

0

Replies

0
Re: Junit5 Mockito for Acitvate method - Adobe Experience Manager 23-03-2021
As pointed out by @Jörg_Hoh , there's an even better way of doing it! Create a map with the properties you want to pass to your serviceMap parameters = new HashMap<>(); parameters.put("my_property","my property");You can then pass this to your context with the registerInjectActivateService method:context.registerInjectActivateService(myService, parameters); _____________________________________Original answer:What you can do is create a mock-implementation of your OSGI configuration interface. p...

Views

392

Like

1

Replies

2
Re: Unable to add custom device groups (emulators) in Tou... - Adobe Experience Manager 20-11-2020
Hey! In order to be able to use a custom device group on your page, you need to add it to the cq:deviceGroups property on the root of your website. So say you have a website "my-site" under /content/my-site and a custom device group "my-site-devices" under /etc/mobile/groups/my-site-devices, then you can simple add the cq:deviceGroups property on /content/my-site/jcr:content/cq:deviceGroups. AEM will then pick up your custom group automatically. Hope t

Views

144

Like

1

Replies

0
Re: Dependency on com.day.cq:parent:pom:82 in 6.5.6 uber-jar - Adobe Experience Manager 15-10-2020
Hey Created a support case with Adobe customer care, and they pointed out that the way you're referencing the uber jar has changed. As outlined on the SP6 release notes, the new way to include the uber-jar is: com.adobe.aem uber-jar 6.5.6-1.0 Hope this helps! With kind regards Koen

Views

752

Like

1

Replies

0
Re: Configuring Style System for Nested Components - Adobe Experience Manager 22-04-2020
From what I've noticed, it looks like the wrapper div is not being generated when including a component. Because of this, the style system cannot add any classes to it. Adding @decoration=true to the data-sly-resource will include the wrapper div (which is important, because otherwise your cq:htmlTag might not be taken into account).

Views

2.3K

Likes

3

Replies

1