BPMN2 Errors in Quickstart
andi.scharfstein Dec 20, 2012 5:37 AMI've been taking a closer look at jBPM and BPMN2 and noticed that I still can't get all of the SY quickstarts to display without errors, specifically the "bpm-service" has multiple errors.
I get 27 BPMN 2.0 Modeler errors like this:
Description | Resource | Path | Location | Type |
Expression and Language must not be blank | ProcessOrder.bpmn | /switchyard-quickstart-bpm-service/src/main/resources/META-INF | Unknown | BPMN 2.0 Modeler |
These are mentioned in SWITCHYARD-1148 as "bogus", and the issue should be fixed in 0.6, but obviously I'm still experiencing it (using the nightly tools build, 0.7 something something). I tried the nightly build of the BPMN 2.0 Modeler as well as the "stable" 0.1 release referenced in https://docs.jboss.org/author/display/SWITCHYARD/Installing+Eclipse+Tooling, no difference. Same issue using the JBoss Developer Studio 5.0.1 GA.
There is one more error that occurs in the BPMN 2.0 Modeler:
Description | Resource | Path | Location | Type |
Item Definition has no structure | ProcessOrder.bpmn | /switchyard-quickstart-bpm-service/src/main/resources/META-INF | Unknown | BPMN 2.0 Modeler |
Under Eclipse, but not under JBoss Developer Studio, I also get two "regular" errors:
Description | Resource | Path | Location | Type |
FeatureNotFoundException: Feature 'script' not found. (platform:/resource/switchyard-quickstart-bpm-service/src/main/resources/META-INF/ProcessOrder.bpmn, 20, 23) | ProcessOrder.bpmn | /switchyard-quickstart-bpm-service/src/main/resources/META-INF | line 20, column 23 | Problem |
FeatureNotFoundException: Feature 'scriptFormat' not found. (platform:/resource/switchyard-quickstart-bpm-service/src/main/resources/META-INF/ProcessOrder.bpmn, 19, 73) | ProcessOrder.bpmn | /switchyard-quickstart-bpm-service/src/main/resources/META-INF | line 19, column 73 | Problem |
This is using the newest version of everything (Eclipse Juno, JBoss Tools, SwitchYard tools, BPMN 2.0 tools), plus some other configurations I tried that didn't change much of anything.
Since it seems to work on your machines, what am I doing differently?