I'm working on a custom component that I will instantiate as an activity of one of our AEM Form processes. I want to test it as thourouloy as possible before I add it to the AEM forms process. My problem is that I get this error while testing. It comes when I try to run the last result.passivate() command. Is the AEM API supposed to connect to a running AEM forms instance when I test this? If so, where is that configured on my local PC? The weird thing is that I get no error when I passivate in the test-class.
2017-jun-15 09:39:27 com.adobe.idp.Document
ALLVARLIG: DOCS001: Unexpected exception. While doing first time passivation for a document..
com.adobe.idp.DocumentError: Failed to connect to LiveCycle server via RMI. Make sure that the server is running and accessible to this client.
public Document concat(final Document base, final Document addOn) throws IOException
Apart from logging internal variables, if you want to debug the code that you have written you can use remote debugging with Jboss assuming you are using AEM forms on Jboss. Even if you are using any other application server like WAS / WebLogic, remote debugging can be enabled to debug your code
Livecycle component is supposed to be installed in the LiveCycle server for it to be tested. In the link pointed by you, a section points to how you can test your component. Please go through this as it will help you in testing your component.