Red Hat Bugzilla – Bug 1314404
JBOSS BPM Process Model Error
Last modified: 2016-04-04 07:50:20 EDT
Description of problem:
The web based process modeler in JBOSS BPM reports an error when you try and place a boundary event on a scripting task. It reports the following error:
"unable to parse xml : Exception class java.lang.IllegalArgumentException : Boundary events are supported only on StateBasedNode, found node: org.jbpm.workflow.core.node.ActionNode [_7FD9BA47-A0BE-4B4E-B8A8-CB9FF29ABB31]"
A quick search shows this is a known issues that has been fixed. Here is the link to that information: https://bugs.eclipse.org/bugs/show_bug.cgi?id=488290
However, I do not know how to apply this fix to the JBOSS Application in OpenShift since d not control the environment.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Place a scripting task in the process modeler
2.Attempt to drop a boundary event on it (it will not let you).
1. Place an unspecified task into the process modeler
2. Drop a boundary event on it (it will let you)
3. Try to compile the solution (you get the error message)
You can not develop a model that uses a boundary event on a scripting task
You can not compile a model that uses a boundary event on a scripting task
You should be able to place a boundary event on a scripting task and it should compile.
The core process engine does not support boundary events on scripting tasks (only for compensation). The error that is returned is therefore correct. The main reason is that script task are executed synchronously, using boundary events in this case is not useful in general.
Could you explain for what use case you would like to use a boundary event for on a script task?
Additional note: the bugzillas linked are regarding a fix for the Eclipse Bpmn2 Modeler, not the web-based Designer. For Designer, the following might be relevant: https://bugzilla.redhat.com/show_bug.cgi?id=994408
I was working an example from a BPMN book (jBPMN 6 Developer's Guide) that shows a error boundary event on an abstract task that represents a reason why the task can't be completed. This must be an error in the book and I just happened to find an IDE example of a similar... but different issue. Or I am just not familiar enough with BPMN yet to understand what I am asking. I apologize for my error.