condition expression string is restricted to 255 chars (JIRA

[hannes]

I ran into some problems after the upgrade from 3.0 to 3.1 with the new decision condition expressions and their EL.
Because I think that is a bug, I created the http://jira.jboss.com/jira/browse/JBPM-764 Jira issue.

Maybe someone in here has a workaround, perhaps shorten the expression in some kind.

TIA :)

[jkronegg]

We got the same problem while migrating from JBPM 3.0 to 3.2.

Transition conditions where previously (in 3.0) stored in the JBPM_DECISIONCONDITIONS table which had 4000 characters. As JPBM 3.2 is backward compatible, it looks into the old JBPM_DECISIONCONDITIONS to execute the condition.

The problem comes when we want to upload a new process definition with a transition with long condition, such as:

<transition name="toBeClosedOrSent" to="ToBeClosed">
 <condition>
 <![CDATA[#{ (executionContext.getContextInstance().getVariable("oldStatut").get(0).intValue()==2 &&
 executionContext.getContextInstance().getVariable("dosType").get(0).intValue()==3) ||
 executionContext.getContextInstance().getVariable("oldStatut").get(0).intValue()==3 }]]>
 </condition>
 </transition>

The transition condition is now stored into the JBPM_TRANSITION.CONDITION_ column which has 255 characters.

The quick workaround we found is to change the column width:

ALTER TABLE JBPM.JBPM_TRANSITION MODIFY (CONDITION_ VARCHAR2(4000) )

On the long term, we plan to move to Drools for such long and complex expression conditions.

[kukeltje]

On the long term, we plan to move to Drools for such long and complex expression conditions.

Good choice