condition expression string is restricted to 255 character length if the process definition is persistent --------------------------------------------------------------------------------------------------------- Key: JBPM-764 URL: http://jira.jboss.com/jira/browse/JBPM-764 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Environment: Win XP SP2, JDK 1.5.0_06, JBoss4.0.3SP1, MySQL 5.0.18-nt-max Reporter: Hannes Stillerich Assigned To: Tom Baeyens The expression of a condition (in a decision node) gets cut up if it is too long (>255 characters), e.g. <decision name="Check Prerequisition"> <transition name="proceed" to="Planning State"> </transition> <transition name="rejected" to="Error State"> <condition expression="#{(contextInstance.variables['isCLIaffected'] and !contextInstance.variables['CLI_OK']) or (contextInstance.variables['isCAaffected'] and !contextInstance.variables['CA_OK']) or (contextInstance.variables['isCMAaffected'] and !contextInstance.variables['CMA_OK']) or (contextInstance.variables['isREGENaffected'] and !contextInstance.variables['REGEN_OK']) or (contextInstance.variables['isSGSNaffected'] and !contextInstance.variables['SGSN_OK']) or (contextInstance.variables['isRNCaffected'] and !contextInstance.variables['RNC_OK'])}"/> </transition> </decision> Of course a org.jbpm.JbpmException occures (couldn't evaluate expression) which is cause by org.jbpm.jpdl.el.ELException: Encountered "<EOF>", expected one of [".", ">", "gt", ..... But if the processdefinition doesn't get loaded from the db, in other words it is directly defined in the code, the expression string can be longer (in this case 539 characters) and the expression works fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira