Red Hat Bugzilla – Bug 990068
CCE when accessing process variable
Last modified: 2014-08-06 16:11:50 EDT
Created attachment 780528 [details]
Description of problem:
Having process definition with a variable of type Integer. When a process instance is being launched from UI, process variable's initial value is passed into the instance as java.lang.String. When the variable is being accessed (e.g. in script task), CCE is thrown: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer
First time I thought it's a bug in engine and I tested similar scenario without UI. I was able to reproduce the exception only when the process instance was started with parameters where the variable was inserted as String. So I guess there is the same problem. Business-central should initialize process variable correctly according to the variable's type in process definition.
Steps to reproduce:
1. start business-central CR1 on EAP 6.1
2. create / use some project
3. import attached process definition
4. build & deploy the project
5. run new process instance and watch the server log
Version-Release number of selected component (if applicable):
Created attachment 780530 [details]
Radek, the issue is that you most likely used the default form (you have not created any forms and thus default applied) that is shipped with the runtime and it's only there for demo purpose. You should create forms from within designer and then the variables will be set with correct type.Just tested it with last week build of kie-wb but I believe it was already present for quite long time (since form modeler integration).
So the main rule is to use generate all form from designer for all processes that are modeled, that will ensure correct data types will be used.
thanks for the clarification. I agree that this is a feature request without clear benefit. On the other hand, user should be aware that this is just a demo form when he opens it. Please add some notifying text to this form so that no one can doubt it is just for demo purposes.
Added information to the automatically generated forms about it's limitation
Committed to master and 6.0.x
Verified on BPMS-6.0.0.ER4
qe_test_coverage: nothing to test, see comment 3 and 4