Hide Forgot
Eligible languages on script task and sequence flow are different, see the table below: script task label language namespace ----------------------------------------------- java http://www.java.com/java mvel http://www.mvel.org/2.0 sequence flow label language namespace ----------------------------------------------- java http://www.java.com/java drools http://www.jboss.org/drools/rule What languages should be supported? All of these three - java, drools, mvel - or is there any reason to have different set of languages on these elements? Also this should be harmonized with Eclipse designer - see bug 1006964. Moreover, when you choose language on script task, the same language is used for the on-entry and on-exit action. But if you want to fill on-entry/on-exit action on any other type of task, there is no way to choose in which language you should type in and http://www.java.com/java namespace is generated.
(In reply to Radovan Synek from comment #0) > Moreover, when you choose language on script task, the same language is used > for the on-entry and on-exit action. But if you want to fill > on-entry/on-exit action on any other type of task, there is no way to choose > in which language you should type in and http://www.java.com/java namespace > is generated. Sorry, this was not accurate description, the script language property is present in all tasks (and works well) except business rule task - where this property is missing and so the user cannot specify which language should be used for on-entry/on-exit action.
(In reply to Radovan Synek from comment #0) > Eligible languages on script task and sequence flow are different, see the > table below: > > script task > label language namespace > ----------------------------------------------- > java http://www.java.com/java > mvel http://www.mvel.org/2.0 This is correct for all scripts (both script task and on-entry/exit scripts) > sequence flow > label language namespace > ----------------------------------------------- > java http://www.java.com/java > drools http://www.jboss.org/drools/rule All constraints should either be java, mvel or drools.
fixed in designer master and 6.0.x branches. note for onentry/exit actions the user choice will not be considered unless user actually defines an onentry/exit action (default is java).
Verified on BPMS-6.0.0.ER5