AnsweredAssumed Answered

Groovy script runtime errors, reference to original script name

Question asked by cirerenat on Apr 30, 2013
Latest reply on May 1, 2013 by trademak
I am running a pretty complicated flow with other call activiti sub flows and there are a quite number of script tasks, they are pretty simple, but when there's an runtime error, the exception is thrown from the groovy library, something like this
No such property: input for class: Script10
and at that point the class name "Script10" is I assume a random name generated by groovy runtime, it has not related with the name of the script task.

Is the original script task name referenced in somewhere in the exception message (activiti engine rethrows it) ? Can this be an enhancement request ? It would make troubleshooting much easier.