2 Replies Latest reply on Jun 27, 2010 7:17 AM by Nugroho Saputro

    JBPM 4.4 Snapshot: timer expression does not accept EL that return a duration string value

    Nugroho Saputro Newbie

      HI All,

       

      I have a problem when running timer with EL expression on JBPM 4.4 snapshot. I use an EL expression #{provisioningService.checkStatusDelay} that return a duration string like "2 minutes"

       

       

      Previously on JBPM 4.3, the EL gets evaluated correctly and timer works as expected but now 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)

       

       

      Is this a bug or the expected behavior?

       

      Thank you.


      Regards,

      Nugroho