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?

Hi, Did you check this is not ACL's related issue? I guess you are using queryBuilder UI with the admin user   

Hi,Your code seems ok, it sounds to me that the issue is because of Mockito and Java incompatibility versions, can you check this thread: https://stackoverflow.com/questions/41050029/mockito-cannot-mock-this-class Also share which dependencies you are using.   Hope this helps.

Hi, I think you can ask directly adobe support about utility, please open a support ticket and ask for this.

@roberto_eff Please clarify your question for the community, and kindly post everything in English for this community.

Hi,   Sorry, I don’t fully understand your question, but a query string is definitely not the best approach. I suggest creating a servlet that receives a JSON payload containing all the details for page creation. The page creation process should be straightforward. As for the sitemap, it should be u...

As @Sady_Rifat already shared, you will always find an UberJar section in the documentation, please refer to this: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/release-notes#uber-jar

Hi @learningNeverStops ,   Beyond the reasons already shared, I think it has more to do with what the client feels comfortable working with. Sometimes a client is used to a specific CDN provider or has several customizations on top of that CDN. At least, that's the main reason I've encountered in my...