Glad I could help. We too are very new to bpm.
As for the persistence, in our situation we have a very slow process (Months)
which is externally moved forward via a custom webapp, so obviously we need to
persist the token counter. It seemed most logical to us to persist it in the
join at
I recently battled this very issue. Attached is the code for a custom join
node that seems to work in all scenarios. (I edited out some of our specific
code so as posted may not exactly work but you should get the gist.)
|
| public class join implements ActionHandler
| {
|
Answers:
Version: bpm 3.1.2
This is the testcase I am trying to run:
| public void testProcess() throws Exception {
|
| // Extract a process definition from the processdefinition.xml
file.
| FileInputStream fis = new
