You need to move you business logic from jap to service but if you still want to do in jsp then you need to whitelist all bundles and may be you require a code refracting as well. Please see below docs to whitelist all bundles https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager...
It should map to your core bundle symbolic name.
<bundleId>:<subServiceName>=<systemUser>
please also look for below notes on https://experienceleague.adobe.com/en/docs/experience-manager-65/content/security/security-service-users
Administrative sessions in JSPs
JSPs cannot use loginService(), be...
Is it on your local setup or you are facing this challenge on AEMCaS environment. If you are facing this issue on your local the. I would recommend restarting your aem instance to see the change currently coming from repoinit script
I don’t think it’s necessary to use service user at all times to get the resource unless you are doing any write operation in the repo and are only accessing the nodes inside /content folder. Normally /content folder has anonymous read permission so please revisit your design for this specific use c...
I18N is not possible for components user input. For this you need language translation for your project. Follow this document to identify what’s suits your requirements https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/introduction/translation#:~:text=To%20...
Yes you can still achieve this using the embedded or dependencies property of clientlibs placed under /apps using etc.clientlibs.
You need to place test2.js in separate clientlibs and test1.js and test3.js in separate clientlibs and add the test2.js as embedded property in clientlibs containing test...
You can use dependencies or embedded for your use case of having on js file dependencies to other js as you explained in your requirements. See below for details https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/introduction/clientlibs
however for clien...
Uninstalling the service pack from aem installed via package manager won’t work. If you need to work on previous installed service pack on same then you need to work with previous backup instance.
I don’t think there is adobe official documentation for your use case but you can achieve this by writing your custom script on docker file. With script your can create a install folder inside crx-QuickStart and place the service pack inside crx-QuickStart/install
the sevice pack placed inside crx-Q...