[
https://jira.jboss.org/browse/JBPM-2900?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu updated JBPM-2900:
------------------------------
Attachment: JBPM-2900.patch
Attach patch and testcase to achieve this feature.
Timer expression does not accept EL expression that returns a
duration string value
-----------------------------------------------------------------------------------
Key: JBPM-2900
URL:
https://jira.jboss.org/browse/JBPM-2900
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.4
Reporter: Nugroho Saputro
Attachments: JBPM-2900.patch
There is a problem on JBPM 4.4 snapshot when using EL expression
#{provisioningService.checkStatusDelay} that return a duration string like "2
minutes" as timer expression.
Previously on JBPM 4.3, the EL gets evaluated correctly and timer works as expected but I
get the following error on 4.4 snapshot.
09:15:26,535 ERROR [ExecuteJobCmd:42] exception while executing
'ExecuteActivityMessage[59]'
org.jbpm.api.JbpmException: Invalid basedate type:
#{provisioningService.checkStatusDelay} is of type java.lang.String. Only Date and
Calendar are supported
at org.jbpm.pvm.internal.cal.Duration.calculateDueDate(Duration.java:131)
at org.jbpm.pvm.internal.job.TimerImpl.setDueDateDescription(TimerImpl.java:75)
at org.jbpm.pvm.internal.model.ScopeInstanceImpl.createTimer(ScopeInstanceImpl.java:305)
at
org.jbpm.pvm.internal.model.ScopeInstanceImpl.initializeTimers(ScopeInstanceImpl.java:334)
at org.jbpm.pvm.internal.model.ExecutionImpl.createScope(ExecutionImpl.java:264)
at
org.jbpm.pvm.internal.model.op.TransitionStartActivity.perform(TransitionStartActivity.java:82)
at
org.jbpm.pvm.internal.model.ExecutionImpl.performAtomicOperationSync(ExecutionImpl.java:671)
at
org.jbpm.pvm.internal.model.op.ExecuteActivityMessage.execute(ExecuteActivityMessage.java:46)
at org.jbpm.pvm.internal.cmd.ExecuteJobCmd.execute(ExecuteJobCmd.java:76)
at org.jbpm.pvm.internal.cmd.ExecuteJobCmd.execute(ExecuteJobCmd.java:42)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira