When you use the Render Plus component from Avoka in Adobe LiveCycle ES compatibility mode, you experience the following exception at runtime:
java.lang.NoClassDefFoundError: com/adobe/workflow/datatype/form/FormDataTypeInstanceImpl
at com.avoka.workflow.component.renderplus.RenderPlusService.execute(RenderPlusService.java:140)
at com.adobe.workflow.engine.PEUtil.executeAction(PEUtil.java:551)
at com.adobe.workflow.engine.SynchronousBranch.handleExecuteAction(SynchronousBranch.java:110)
at com.adobe.workflow.engine.SynchronousBranch.execute(SynchronousBranch.java:867)
at com.adobe.workflow.engine.ProcessEngineBMTBean.continueBranchAtAction(ProcessEngineBMTBean.java:2773)
at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncContinueBranchCommand(ProcessEngineBMTBean.java:2436)
at com.adobe.workflow.engine.adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.asyncContinueBranchCommand(adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.java:2228)
at com.adobe.workflow.engine.ProcessCommandControllerBean.doOnMessage(ProcessCommandControllerBean.java:144)
at com.adobe.workflow.engine.ProcessCommandControllerBean.onMessage(ProcessCommandControllerBean.java:99)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3962)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Contact the component vendor and ensure that you are using the latest version of the component in LiveCycle ES. For the latest Avoka components, check the Avoka website.
This exception appears when the component has not been updated to support the lc7form variable type.
The following information can be found in the Upgrading documentation for LiveCycle ES: http://help.adobe.com/en_US/livecycle/8.2/upgrade_changes.pdf.
Custom components provided by Avoka sometimes must be replaced in LiveCycle ES with updated versions so that they continue to work properly. After upgrading to LiveCycle ES 8.2, deploy the updated components to the LiveCycle ES server. Check with your third-party vendor or your developers before upgrading to determine whether these updates are required.
Adobe LiveCycle Workflow 7.x supported a series of variable types that you can use in process definitions. The form variable type is renamed lc7form when you upgrade to LiveCycle ES. The upgrade automatically updates your processes to use the new variable type name; in most cases, the change is transparent. If you use a custom component, and it references the form variable type, update the component to recognize the lc7form variable type name. The new component must then be deployed to the server from Adobe LiveCycle Workbench ES.
Keywords:
cpsid_80631
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
