1 2 Previous Next 17 Replies Latest reply on Jul 28, 2008 10:21 AM by Tom Baeyens

    Support of variable in timerDefinition

    Pascal Verdage Newbie


      As it has already been discussed in the post on Expression Language0 (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155029#4155029), support of variables in timerDefinition would allow more flexibility in the use of timers.

      "kukeltje" wrote:
      - setting timers dynamically based on processvariables
      - choosing a specific subprocess runtime instead of designtime

      Furthermore, this is promoted in specifications. In BPEL-2.0, specification of the Wait activity (http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html#_Toc164738509) explains that:
      A typical use of this activity is to invoke an operation at a certain time (in this example a constant, but more typically an expression dependent on process state)

      Dependent on process state means to my mind using a variable.

      Plus, this feature is blocking to use TimerDefinition in Orchestra since this is the more common way Pick and Wait activities are used. So we still create timers at runtime.

      Do you think it would be possible to add this feature to the pvm: using process (or node) variables to define a timer's dueDate?
      Or should this wait until the expression language is supported (as you said, in the future ;))


        1 2 Previous Next