7 Replies Latest reply on Jul 19, 2006 11:15 AM by falazar

    Strange message

    j1a2o

      When a task-node has multiple tasks, I get "New tasks have been assigned to: null, null, null, null, null, null." on assignment instead of "New tasks have been assined to: <user 1>, <user 2>, etc."

      Is there a reason why it does this? Thanks.

        • 1. Re: Strange message
          kukeltje

          which version of jbpm are you using 6.03? On JBoss 11?

          • 2. Re: Strange message
            j1a2o

            Not quite sure. I downloaded jbpm-starters-kit-3.1.1.

            • 3. Re: Strange message
              cpob

              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.

              • 4. Re: Strange message
                kukeltje

                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.

                • 5. Re: Strange message
                  j1a2o

                  Can you explain what you mean by reused?

                  This is one of my swimlanes:

                  <swimlane name="Engineering">
                   <assignment expression="user(ernie)"></assignment>
                  </swimlane>
                  


                  Thanks.

                  • 6. Re: Strange message
                    cpob

                    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)

                    • 7. Re: Strange message

                      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?

                      James Ratcliff