topic Re: Eclipse plug-in unable to instantiate class 'org.activiti.designer.eclipse.editor.ActivitiDiagramEditor' in Alfresco Archive

Eclipse plug-in unable to instantiate class 'org.activiti.designer.eclipse.editor.ActivitiDiagramEditor'

peilers — Tue, 02 Dec 2014 16:30:26 GMT

I have just build the Activiti Designer plug-in from the source on Github using the following steps:1. Import the source from the Github clone uri into a Git project2. Update the pom.xml in org.activiti.designer.parent to reference luna instead of juno3. Navigate to the local git repository org.acti

Re: Eclipse plug-in unable to instantiate class 'org.activiti.designer.eclipse.editor.ActivitiDiagramEditor'

peilers — Tue, 02 Dec 2014 20:56:49 GMT

I have also attached the .classpath file for org.activiti.designer.libs (there is no ./ entry and all bpmn jars seem to be there). I also have the latest versions of the EMF and Graphiti plug-ins installed.

Re: Eclipse plug-in unable to instantiate class 'org.activiti.designer.eclipse.editor.ActivitiDiagramEditor'

peilers — Tue, 02 Dec 2014 21:51:21 GMT

RESOLUTION:
For the benefit of others (since there are several permutations of these instructions available across Codehaus and the forum), these are the steps that I performed to result in a successful build of the Activiti Designer:
1. Start with clean workspace with EMF and Graphiti installed and up to date.
2. Import the Activiti Designer source into the workspace via:
     File/Import/Git/Projects from Git. Select "Clone URI" and provide: https://github.com/Activiti/Activiti-Designer.git as the URI.
     Select the "master" branch. Select "Clone submodules".
     Selected "Import as general project" (Default value "Import existing projects" found no projects)
3. View the pom.xml in the parent Maven project –> it references Eclipse Juno version
     Updated references from Juno to Luna
4. Updated manifest.mf (in org.activiti.designer.libs) to remove the ".,/" entry
5. Went to the Runtime tab for manifest file (in org.activiti.designer.libs) and Added (3) jar files as follows:
     org.activiti.designer.libs/activiti-bpmn-converter-5.16.2-SNAPSHOT.jar
     org.activiti.designer.libs/activiti-bpmn-layout-5.16.2-SNAPSHOT.jar
     org.activiti.designer.libs/activiti-bpmn-model-5.16.2-SNAPSHOT.jar
6. Executed >mvn clean eclipse:clean –> BUILD SUCCESS
7. Executed >mvn eclipse:eclipse –> BUILD SUCCESS
8. File/Import/Existing Projects into Workspace (Search for nested projects from local repository into workspace)–select each of the projects one-by-one so that they create top level projects. NOTE: Import the libs project first.
9. File/Import/Maven/Existing Maven Project
10. Repeat #5 above (unknown why this is required)–add jar files again to org.activiti.designer.libs in the Classpath pane of the manifest.mf Runtime tab:
     org.activiti.designer.libs/activiti-bpmn-converter-5.16.2-SNAPSHOT.jar
     org.activiti.designer.libs/activiti-bpmn-layout-5.16.2-SNAPSHOT.jar
     org.activiti.designer.libs/activiti-bpmn-model-5.16.2-SNAPSHOT.jar
11. Selected all top level Activiti Designer projects and performed File/Refresh
12. Selected Project/Clean for all projects (at this point there are no project level errors…progress)
13. Selected the plugin.xml (overview tab) for org.activiti.designer.eclipse and chose to "Launch Eclipse Application" to verify that creating an Activiti Diagram succeeds without errors.

Re: Eclipse plug-in unable to instantiate class 'org.activiti.designer.eclipse.editor.ActivitiDiagramEditor'

jbarrez — Fri, 05 Dec 2014 15:26:17 GMT

Thanks for sharing this!

Re: Eclipse plug-in unable to instantiate class 'org.activiti.designer.eclipse.editor.ActivitiDiagramEditor'

peilers — Fri, 05 Dec 2014 15:40:55 GMT

By the way, I ended up adding all of the JARs from the libs project to the Classpath list via the Manifest.mf editor (not just the 3 mentioned in my post above) since I continued to get errors as I put the Designer plug-in through its paces.

Also, there is a step missing in setting up the initial Eclipse environment as follows from the Codehaus instructions:
"In order to have BPMN code completion and validation, import BPMN's XML Schemas from activiti-engine/src/main/resources/org/activiti/impl/bpmn/parser into the Eclipse XML Catalog, which can be found in Preferences –> XML –> XMLCatalog."

Re: Eclipse plug-in unable to instantiate class 'org.activiti.designer.eclipse.editor.ActivitiDiagramEditor'

peilers — Fri, 05 Dec 2014 15:48:43 GMT

So the final instruction steps would now be:

1. Start with clean workspace with EMF and Graphiti installed and up to date.

2. Per the instructions on Codehaus, "In order to have BPMN code completion and validation, import BPMN's XML Schemas from activiti-engine/src/main/resources/org/activiti/impl/bpmn/parser into the Eclipse XML Catalog, which can be found in Preferences –> XML –> XMLCatalog." (Created the files in the BPAWorks directory)

3. Import the Activiti Designer source into the workspace via:
File/Import/Git/Projects from Git. Select "Clone URI" and provide: https://github.com/Activiti/Activiti-Designer.git as the URI.
Select the "master" branch. Select "Clone submodules".
Selected "Import as general project" (Default value "Import existing projects" found no projects)

4. View the pom.xml in the parent Maven project –> it references Eclipse Juno version
Update references from Juno to Luna (or whatever version of Eclipse you are using).

5. Update build.properties for the manifest.mf (in org.activiti.designer.libs) to remove the ".,/" entry

6. Go to the Runtime tab for the manifest file (in org.activiti.designer.libs) and Add all jar files to the Classpath list.

7. In a console window, navigate to the local Git repository and to the org.activiti.designer.parent directory. Execute >mvn clean eclipse:clean –> BUILD SUCCESS

8. Still in the org.activiti.designer.parent directory, execute >mvn eclipse:eclipse –> BUILD SUCCESS

9. File/Import/Existing Projects into Workspace (Search for nested projects from local repository into workspace)–Select each of the projects one-by-one so that they create top level projects. NOTE: Import the libs project first.

10. File/Import/Maven/Existing Maven Project to import the org.activiti.designer.parent project

11. Repeat #5 above (unknown why this is required)–add all jar files again to org.activiti.designer.libs in the Classpath pane of the manifest.mf Runtime tab.

11. Selected all top level Activiti Designer projects and performed File/Refresh

12. Selected Project/Clean for all projects

Note that depending on the version of the Graphiti plug-in you may need to change the reference to the Graphiti feature within the org.activiti.designer.feature project (via the feature.xml editor).

Re: Eclipse plug-in unable to instantiate class 'org.activiti.designer.eclipse.editor.ActivitiDiagramEditor'

dbmalkovsky — Wed, 10 Dec 2014 17:19:26 GMT

I've been working on a similar issue and have made some changes so you don't have to modify the parent pom for different eclipse versions but rather specify a profile to Maven that defines the appropriate paths for the repositories, etc.

The problem that I am left with is not understanding why the MANIFEST.MF file is re-written by the <code>mvn eclipse:eclipse</code> process. Each MANIFEST.MF file is change in all the sub-projects. In the org.activiti.designer.libs project it removes the <code>activiti-bpmn-……jars</code> from the original MANIFEST.MF file as part of the re-rewrite. The jars exist in both the original MANIFEST.MF and the build.properties files. The classes in those jars are referenced in the Export-Package list. I am further confused as to why the <code>activiti-simple-workflow-alfresco-5.16.2-SNAPSHOT.jar</code> is retained in the MANIFEST.MF file. I've played around with different Export lists, build.properties values, etc. but cannot seem to find a pattern. FWIW, I've tried with and without step #5 above. I've run Maven with <code>–debug</code> and examined the output without any further insight into the issue.
I hope that someone who understands Maven and the MANIFEST semantics better than I can explain why the necessary Activiti jars are removed from the classpath in the MANIFEST.MF during the <code>eclipse:eclipse</code> processing so that the manual step (#6) to add them back in is no longer required.

Thank you in advance.

Re: Eclipse plug-in unable to instantiate class 'org.activiti.designer.eclipse.editor.ActivitiDiagramEditor'

chockyc91 — Sun, 29 Mar 2015 15:01:51 GMT

Dear peiler,
I have tried the above steps as informed by you. But I couldn't open the activiti diagram editor.

Kindly help.
Thanks in Advance.