1: there seems to be an issue if a swimelane is used on more then one task. I've ran into this myself and are investigating it
2: do you use an in memory database?
1. No, I don't use an in memory database. I use MySQL.
2. I have only one task.
ps. I've solved my problem no. 1. There was a wrong package name.
Does it occur only on tasks defined in the start-state, or also those defined on tasknodes?
Ive tested only for start-state.
but i think it will appear for all other tasks.
BTW, if i use setActorId('ernie') after i create the startTask, everithing is fine...the task is added to ernie's task list.
The question is why the actorid is not assigned from the swimlane ? Do i have to assing it manually ? But again, then, why does it work sometimes as it is now ?
I hope it is not because the swimlane class is commented out :-)
The start state can be executed by anyone, it is not assigned (known 'issue', no statement on it yet..... ) We are thinking about this.
For preventing others to start it, he webapp should/could detect if the actor that is allowed to act on the start state is the same that is in the swimlane.
As mentioned earlier, reused swimlanes set an actorid with value null on the second task they are used on.
i created http://jira.jboss.com/jira/browse/JBPM-375 to keep track of this issue...
if anyone knows more (like wether it is a bug, a test case or where the problem is located in the code) please add it as a comment to that issue.
i'm looking into it tonight, since I have a problem myself. It seams (no pun intended, although I cannot find the time to look into it, sounds promissing) that if a swimlane is used the second time, the assignmenthandler is not called and the actorID of the task becomes null instead of staying/becomming the same as it was the firsttime the swimlane was used.
I'll keep you posted