Thanks Arun, this example is nice, but uses ConfigurationAdmin API. I was looking for example using R6 annotations way of reading OSGi configuration.Regards,Sandeep

Thanks smacdonald2008​. Is there a way to read non-custom OSGi configuration e.g. Day CQ Mail Service etc in our code? Using ConfigurationAdmin we could directly get configurationconfigurationAdmin.getConfiguration("PID of OOTB config");Annotations seem to be working fine for custom application spec...

Thanks JörgIt seems the AEM Core Components has Page Model implementation. This has a methodprivate <T> Map<String, T> getChildModels(@Nonnull SlingHttpServletRequest slingRequest,                                              @Nonnull Class<T> modelClass) {        Map<String, T> itemWrappers = new L...

Thanks @snaomi0705. This is working fine when we are associating condition with goal metric (Once goal metric is achieved for that user, user not shown that activity at all again).I think for just view of experience without attaching goal metric there is no OOTB way to show experience once per user....

Hello smacdonald2008​,Thank you for your response. The way you shared is one way to test the Model classes (inside core folder). it.launcher and it.tests folders are still not clear, what is the use in project structure and when they are run.Regards,Sandeep

Got information from Github repo (we-retail-journel reference package · Issue #9 · Adobe-Marketing-Cloud/Summit2018 · GitHub ). The package is not public yet. We would have to wait till June/July for Adobe to release this it seems.

Thanks smacdonald2008 for response.Is there a recommendation for the limit that Adobe recommends e.g. upto 500 nodes Traversal is better, more than that use indexes and queries.

It seems the screenshots in documentation have been given from we.retail sandbox component. The documentation doesn't mentions about the sandbox content fragment component. After installing we.retail sandbox component the model selector is working fine. Not sure why "General" Content Fragment compon...

It seems the screenshots in documentation have been given from we.retail sandbox component. The documentation doesn't mentions about the sandbox content fragment component. After installing we.retail sandbox component the dialog is coming as shown in documentation.

Seems like the Caas feature is overridden by Sling Model Exporter. Below is the quote from reference link Adobe is probably trying to reuse feature provided by Sling instead of reinventing the wheel, also focusing on providing headless capabilities to cater to different channels/type of apps. I gues...