Appreciate for hepls... being trying this for few days...:(
I am trying to build a customize component to use in a process using adobe java API. I follow the document and include all the necessary lib files. It compiled with no errors. And I pack it into JAR file and deploy to the workbench, no error. Then I call the customized component method and it throw the error as below, is merely cause by "Caused by: java.lang.NoClassDefFoundError: com.adobe.idp.taskmanager.dsc.client.TaskManagerClientFactory
". Portion of my code is as follow.
What did I miss out? I include the libs file as stated in the document. Do I need to specify the class-path in a manifest file? How? It is not mentioned in the document. Is the "adobe-taskmanager-client-sdk.jar" pack in one of the ear or war file in the App server's (I'm using websphere) installedApp directory?
Really appreciate for help... Is there any documents describing the deployment details. The sdk document is not very detail...
I manage to solve the NoClassDefFound problem in any other way. Will try your method.
What I do is I add the adobe-taskmanager-client-sdk.jar file to my customize component jar file (at root). And I add the classpath tag for the adobe-taskmanager-client-sdk.jar to the component.xml file. But when the customise component is run at a process. Another problem occured. I got an exception "com.adobe.idp.taskmanager.dsc.client.query.TaskRowImpl incompatible with com.adobe.idp.taskmanager.dsc.client.query.TaskRow".
Try running the code from a standalone Java application. Once you know whether the code works in a standalone application, put it in a component. You do not need to include LC JAR files in your component's JAR file. As explained in the docs:
It is recommended that you include only the JAR files that are required to run the Java application logic located in your component. That is, if a JAR file is not required by your component, do not include it in the component JAR file. Although you must include adobe-livecycle-client.jar in your projects class path to use a com.adobe.idp.Document object in your application logic, it is not necessary to include this JAR file in the component JAR file because this data type is already part of the service container.
It sounds like you may be getting a class loader conflict. Try not including the Adobe LiveCycle jars in your package (they are already on the server). Instead modify your component.xml to include the Adobe classes in the <dynamic-import-packages> tag.