Hi @Babita11 You should not throw generic exceptions. You should be subclassing Exception and then throwing your subclass, so that the type of the exception actually provides information about what is going on, allowing clients of the function to catch and treat it appropriately. Example:Here Exceptio is generic in nature and you should not be using it. Instead of that you should use the specific category type i.e., either "LoginException", "RepositoryException", depending upon the nature of exc...

Hi @flavortron You can use the selector based approach if I understood the ask properly. Let's say you have different component called abc and xyz. Now each of the component will have it's own script i.e., abc.html and xyz.html. if you want to check the preview, you might include another script i.e., preview.html in each of the component and then you can access the page with pageurl.preview.html. This will ensure the preview.html script for each component to load and you can see the preview inst...

Hi @skattamuri Have you updated the uber jar version to 6.5.11 ? Also are you getting error in compile time or runtime? com.adobe.aem uber-jar 6.5.11 provided Also upgrade the JAXB Maven dependency to latest version. javax.xml.bindjaxb-api2.2.3 Thanks!

Hi @Hugh_Shao You should be able to navigate to "Content Tree" section by clicking on the "Toggle Side Panel" and it will allow you to see all the components used on the page if you are not able to see it in edit mode. Thanks!

Hi @chiaraT This is a dedicated community only for Adobe Experience Manager Site related platform. Can you please post the question in AEM Forms forum to get the better and quicker response? https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/ct-p/adobe-experience-manager-forms-community Thanks!

Hi @rajanin89039659 Connection refused error comes only when your instance is not reachable with the IP and PORT that you have configured. So please check if the instance is accessible with same HOST and PORT. Thanks!

Spoke with Adobe and unfortunately there is no solution ready to go. Adobe is heavily working on this thing, because a lot of clients are requesting this. Only way to fix this is to split the packages into multiple package and deploy it to other environment. Let's see when Adobe will come with a feasible solution! Thanks!