From do-not-reply at jboss.com Wed Oct  1 08:49:30 2008
Content-Type: multipart/mixed; boundary="===============7453937539412674135=="
MIME-Version: 1.0
From: juergen_lampe <do-not-reply at jboss.com>
To: jbpm-users at lists.jboss.org
Subject: [jbpm-users] [JBoss jBPM] - Re: Timers in jBPL
Date: Wed, 01 Oct 2008 08:49:30 -0400
Message-ID: <7532370.1222865370895.JavaMail.jboss@colo-br-02.atl.jboss.com>

--===============7453937539412674135==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

I think so. It should be started via the web.xml entry:
    <!-- Job executor launcher (begin) -->
  |     <listener>
  |         <description>
  |             Starts the job executor on servlet context initialization a=
nd stops it on =

  |             servlet context destruction.
  |         </description>
  |         <listener-class>org.jbpm.web.JobExecutorLauncher</listener-clas=
s>
  |     </listener>
  |     <!-- Job executor launcher (end) -->
  | =


Meanwhile I played around a bit:
1) changed the timer to
         <timer name=3D'reminder' =

  |                 duedate=3D'2 minutes' =

  |                 transition=3D'ex1' >
  |              <script>
  |                System.out.println("Timer fired "+node);
  |                Token.signal();
  |              </script>
  |          </timer>
  | =

got the output "Timer fired State(warte 1)" but nothing else.

2) changed the script to =

             <script>
  |                System.out.println("Timer fired "+node);
  |                executionContext.getProcessInstance().signal();
  |              </script>
  | =

found the server locked in endless printing "Timer fired State(warte 1)"

View the original post : http://www.jboss.com/index.html?module=3Dbb&op=3Dv=
iewtopic&p=3D4179782#4179782

Reply to the post : http://www.jboss.com/index.html?module=3Dbb&op=3Dpostin=
g&mode=3Dreply&p=3D4179782

--===============7453937539412674135==--