Hi @adimangalampalli WCM io library is a utility to mock AEM resources during test time. If you have created a new static method then please avoid using creating a static method as this won't be considered as best practice in java and for the same reason mockito framework doesn't provide the capabil...

@Mario248 It seems like the jar you mentioned above is depending on this jar which is not resolving as a bundle. Could you please add this jar as well in all/pom.xml like the one you mentioned in the problem statement and follow the same steps for this one and see if it works?Regards, Arpit Varshney

Hi @Mario248 The above steps look fine but I didn't see the dependency used in the core module where you want to use the corresponding classes. You might need to add the dependency in the core module pom.xml along with the parent pom. <dependency> <groupId>software.amazon.awssdk</groupId> <artifac...

Hi @prahlad-dutta Have you verified with the same amount of content locally where it worked? You might need to check error logs and thread dumps if there is any relevant information.Regards, Arpit Varshney

Hi @rahul234dabas It seems like your custom code is using a session or resolver derived from the anonymous user which doesn't have DAM write permission. Usually, these scenarios are handled using the service resolver concept.Check this:https://experienceleague.adobe.com/docs/experience-manager-64/ad...

Hi @PolinaVinni This doesn't seem to be the OOTB behavior of AEM multifield. It seems either your multifield structure in the dialog is not proper or there is some customization happening in your custom code via JS related to multifield. Please check.However, you can validate it on vanilla AEM(witho...

Hi @test566    It might be possible that your project has some custom solution in the codebase.   check for any servlet if registered using path or resource type: URI=/etc/replication/agents.publish.json   I hope this is not coming in AEM vanilla instance(without custom code) so you need to debug fu...

Hi @JakubLG It usually takes some time to reflect in the software distribution portal, however, if this is quite urgent for you then you can raise an Adobe support ticket. they should be able to help you answer with better clarity.   Regards, Arpit Varshney

Hi @HanL1 Have you verified after deploying the code, whether your bundles are active or not? Please validate the /system/console/bundles.If bundles are not active and the added jar is not getting resolved that means the given dependency is not available as a bundle in the target AEM.You can follow ...

Hi @dh54220    CRUD operation in node can happen via sling(treat as resource)or node api which can only be done via server side.   You can use server side approach with above api.   Regards, Arpit Varshney