Bug 1181455

Marco, is there a reason why potential owners are not populated in the remote jaxb tasks?  It seems to be reported against 6.0.x so maybe already fixed in 6.1.x?

Additionally,

getActualOwner
getCreatedBy

always returns null no matter what.

I'd prefer to not implement this on the level of query - and be returned as part of TaskSummary as it will make the query operation rather heavy. Collecting all potential owners for all found tasks might become a performance issue. Thus I would like to suggest following:
- do the query first
- for whatever task you need details get them via getTaskById method which will return potential owners as well.

This way we stay in good shape when it comes to performance and still provide all required information. Moreover this is exactly the same way we do on UI side. Display the details only for individual tasks on demand.

When it comes to ActualOwner and CreatedBy they do provide valid entries but in 6.1 you should rather rely on getActualOwnerId and getCreatedById which will return directly the id of the actor rather than User object instance.

So my vote is to set it to modified to retest the actual owner and created by functionality and do not change code base for loading more data at query time.

Maciej,

I have tested the following:

for (TaskSummary sum : list) {
System.out.println("task pot own:"+sum.getPotentialOwners()); // this is null

Task task = taskService.getTaskById(sum.getId());
List<OrganizationalEntity> org =  task.getPeopleAssignments().getPotentialOwners();
				
for (OrganizationalEntity ent: org) {
				
System.out.println("org:"+ent.getId()); //expected result
}
				
}

taskService.start(list.get(0).getId(), "anton1");
		
		System.out.println("ActOwn:"+taskService.getTaskById(list.get(0).getId()).getTaskData().getActualOwner().getId()); //expected
System.out.println("ActOwn1"+list.get(0).getActualOwner()); //null

I think this is what you have had in mind? If so, I am pretty satisfied with the behavior. The only thing which needs to be adjusted is documentation, so the customers know that it is expected that calling getPotentialOwners on TaskSummary remotely will give you null result and you need to fetch the Task object in order to get this information.

Anton.

yes, that is exactly what I had in mind. Good then I'll transfer this to docs team as there won't be any code changes for that.

@Vikram, could you please add that to the docs - conclusion from comment 5?

I have documented this in the new Development Guide here [1] as a note.

Please verify if the note accurately describes the resolution for this issue.

Moving this to ON_QA for a 6.1 release (and NOT for 6.0 async release as it contains methods that are in 6.1 - getActualOwnerById and getCreatedById())

[1] http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html-single/Development_Guide/index.html#The_REST_Remote_Java_RuntimeEngine_Factory

Thanks Ivo. I have shortened the text at the start. This can now be verified here [1].

Moving back to ON_QA.

[1] http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html-single/Development_Guide/index.html#The_REST_Remote_Java_RuntimeEngine_Factory

That's perfect Vikram, thank you. Verified in [1]

[1] http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html-single/Development_Guide/index.html#The_REST_Remote_Java_RuntimeEngine_Factory