Hi.
Seems that org.kie.services.remote.util.Paginator should not be needed.
Instead, it seems that raw database pagination should be utilized via JDBC and hibernate as per functionality provided in org.jbpm.shared.services.impl.JbpmServicesPersistenceManagerImpl (line 525 ).

But to take advantage raw database pagination, it seems that there are some core jbpm human task changes to be made:

1) org.jbpm.services.task.identity.UserGroupTaskQueryServiceDecorator

• only one function currently allows for pagination parameters as part of the query . Seems that all of the functions should.

2) CommandPattern classes do not accept pagination parameters. ie: GetTaskAssignedAsPotentialOwnerCommand .

once these jbpm human task issues are addressed, it seems that the execution server can delegate pagination to the database, correct ?

thanks! jeff