| [Xpand] Running Xpand Workflow via Equinox Launcher [message #989531] |
Thu, 06 December 2012 11:23  |
Eclipse User |
|
|
|
I have a workflow that works with Xpand and does of fine job of generating the code I need when I run it from within the Eclipse Workbench (the usual right click/Run As).
But we want to run from console (actually a build script) as this is only part of a larger product build. While the doc does give the WorkflowRunner class, to run it directly requires setting up a classpath to a large number of jars in the eclipse/plugins directory, which we would prefer to avoid.
So instead I tried to use the Eclipse Equinox Launcher. The command line I used was :
java -jar /opt/eclipse/plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar -application org.eclipse.emf.mwe.core.WorkflowRunner src/workflow/ddmGenerator.mwe
This seems to launch the Workflow OK, and we get through the load ecore steps, when we get to Check (which does no actual checks, but works OK within Workbench), we fail on null pointer exception that appears to be deep inside the component code (log file attached).
So, the question is, has anyone successfully used Equinox to run an Xpand workflow? Or have then done the base standalone with a hand generated classpath ?
Thanks for your time
Dale Pennington
Attachment: log
(Size: 5.49KB, Downloaded 272 times)
|
|
|
|
| Re: [Xpand] Running Xpand Workflow via Equinox Launcher [message #989579 is a reply to message #989542] |
Thu, 06 December 2012 15:20  |
| Eclipse User |
|
|
|
You know, I tried the runnable jar file wizard, but stalled on step 2, as there were no options under Launch Configuration.
As far as I can tell, what I should be exporting is runner, not my Xpand project. Also that still leaves future issues of what I need to check into the CM system and what I edit (which should be under CM) when modifing stuff.
Part of it is understanding what the workflow needs actually, and what is also being done for me under the covers by Eclipse. I suspect my issue is the standalone run is not doing the Eclipse special helping steps (like compiling the java extensions into a .class file).
I am going to attempt to do the standalone option, just to see if I get the same issue (i.e. the logged error seemed to hit in the workflow, not the launcher, so I suspect my problem is at a lower level).
Dale
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.06369 seconds
Home