1 Reply Latest reply on Dec 16, 2008 4:25 PM by kukeltje

    jpdl 3.2.3 -> 3.3 and new behavior of getGroupTaskList()

    nilian

      Hi,

      we migrated from jpdl v3.2.3 to v3.3 and did see some new behavior for
      "JBPMContext.getGroupTaskList(List actorIds)".

      In our scenario we assigned the same task to two groups of users (two pooledActorIds. Calling "JBPMContext.getGroupTaskList(List actorIds)" with these two groupidents returns a list of with one Taskinstance as expected.

      The same scenario with the new jpdl v3.3 will get you a list with two items, which are two references to the same Taskinstance.
      Digging into the code there was a change in the corresponding hibernate-query ("TaskMgmtSession.findPooledTaskInstancesByActorIds" in hibernate.queries.hbm.xml).
      The 3.2.3 version uses the "distinct" keyword, while the 3.3 one does not.

      Is this new behavior intended or some kind of bug ?

      Best regards,
      Daniel Bremer-Tonn

        • 1. Re: jpdl 3.2.3 -> 3.3 and new behavior of getGroupTaskList()
          kukeltje

           


          Is this new behavior intended or some kind of bug ?

          It's one of both ;-) well... it could be that it was un-intentional but the, in hindsight, required behaviour... Totally not sure. Please file a jira issue since it is a change and should be documented somewhere or fixed. File it e.g. with a description of 'getGroupTaskList(List actorids) behaviour changed'