which version of jbpm are you using 6.03? On JBoss 11?
Not quite sure. I downloaded jbpm-starters-kit-3.1.1.
It's a bug, you're using 3.1.1 with that starter's kit.
It's a bug in the sample webapp, and if you dig into it, you can fix it.
I know I've seen it before, and I think it's come up in the forums before. Not sure if there's a Jira issue, but since 3.1.1 webapp isn't a huge focal point (due to the new changes in 3.2) it might not be fixed.
I've only seen 'null' in the responding text if the swimlane was 're-used' with an already filled actor field.
But I can mis some things.
Can you explain what you mean by reused?
This is one of my swimlanes:
<swimlane name="Engineering"> <assignment expression="user(ernie)"></assignment> </swimlane>
I only see this in the 3.1.1 webapp when there are multiple tasks assigned, like when you have a fork to two task nodes. I made the fix once in the webapp...
I just checked. In TaskBean.java, line 202, it calls the wrong method.
msg += taskAssignLog.getActorId();
That should be .getTaskNewActorId(); (Which is called properly on line 195)
I noticed this as well wen using a fork for more than one user, or for using groups.
This is fixed in the 3.2 version however? For the webapp?