JBossDeveloper

I partly agree with you, API should be kept as simple as possible

But assigning tasks to no existig users will in fact result in possible troubles with finding these tasks, which will result in maintenance issues. This is the case especially when assignment is evaluated on runtime based on user input.

According to jira, it was intended to have such validation.

About reassigning task in case all of the appointed users are not available should be (in my opinion) be an administration issue. If you design it to have assignment be done on a group level you could have always an option to add new user to one of the groups.

That's my two cents.

hi Sebastian,

did you try something like this:

     Set<ParticipationImpl> participations = task.getAllParticipants();
        for (ParticipationImpl participation : participations) {
            System.out.println(
                    "type: " + participation.getType()
                    + " user: " + participation.getUserId()
                    + " group: " + participation.getGroupId());
        }

This is what I use the populate the dropdown in my reassignment screen:

Get the participations like Michael suggested or through an hql query and then loop through the them to find the users:

    
    for (Participation participation : participations) {
        if (participation.getUserId() != null) {
            users.add(participation.getUserId());
        }
        else if (participation.getGroupId() != null) {
            List<User> groupUsers = noTxCmdService.execute(new FindUsersInGroupCmd(participation.getGroupId()));
            if (groupUsers != null) {
                for (User groupUser : groupUsers) {
                    users.add(groupUser.getId());
                }
            }
        }
    }   

FindUsersInGroupCmd:

    public List<User> execute(Environment environment) {
        IdentitySession identitySession = environment.get(IdentitySession.class);
        return identitySession.findUsersByGroup(groupId);
    }

Hope  this helps

Walter

Hi, I have the problem of null IdentityService, how did you solve it? I don't see what did you change in the end, in jbpm.cfg.xml or in applicationContext-process.xml, to make it work...

I'm using jbpm 4.4

Thanks

Dámaris.