Hi @shafali12  The short answer is no. The problem is that what you are trying to do is conceptually wrong. The idea behind the style system is to leverage functionality at the template (policies) level. This is a completely different approach compared to having dialog configurations that are compon...

@KannanCh2    If you are asking if you can get rid of Adobe's CDN, the short answer is NO. This is part of the Architecture of AEMaaCS, you can bring your own CDN and add it on top of Adobe's CDN but it is not really a swap nor a replace.Hope this helps

Hi,    This is a known issue in acs-commons: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2146. this is apparently solved, so please try a newer version of acs that include the fix mentioned in the thread.   Hope this helps

Hi,   The @OSGIService annotation is specific for sling models, you cannot use it outside a sling model, in other words, it is expected to get null if you are using this annotation within an OSGI service. Check the official doc: https://sling.apache.org/apidocs/sling8/org/apache/sling/models/annotat...

Hi, I don't think there is an official approach on how to do this, but in reality, it is not that complicated. You just need to keep in mind that you simply need to invoke a correctly formatted URL and/or load the proper JS (if you are using one of the viewers). With that in mind, you can check how ...

Hi, If this is local and you don't have anything new, it is easier to start a new instance, just delete the crx-quickstart folder. If you cannot delete the instance, you could try checking the bundles and ensure everything is in "active" state, go to /system/bundles. Also check this thread as well: ...

Hi,  Since the SPA remote actually just "loads" the SPA app into the SPA editor, the SSR needs to happen in the apps. That being said, there are a couple of ways to achieve SSR. I think the easiest way, because of the examples and boilerplate, is to use NextJS, which already ships with SSR capabilit...

Right, the attribute will tell which resource to look in a specific path, but you need to load such resource in the path, so the AEMcontext can get it

You should create the page and load its properties as part of the aemContext so below line actually can retrieve the page's properties: pageManager.getPage(productModelPage); Try something like this https://wcm.io/testing/aem-mock/usage-content-loader-builder.html:   Hope this helps 

Hi, How are you mocking the page? Can you post some code to see what is going on?