cancel
Showing results for 
Search instead for 
Did you mean: 

Pagination/Sorting not working using Task Query REST API

aggiepilot04
Champ in-the-making
Champ in-the-making
According to the documentation, this should work…but we get the error below (and ultimately, a 405).

<blockcode>
<Jan 27, 2014 4:12:43 PM org.restlet.ext.jackson.JacksonRepresentation getObject
WARNING: Unable to parse the object with Jackson.
org.codehaus.jackson.map.exc.UnrecognizedPropertyException: Unrecognized field "size" (Class org.activiti.rest.service.api.runtime.task.TaskQueryRequest), not marked as ignorable
at [Source: org.restlet.engine.http.io.UnclosableInputStream@24c75c8c; line: 8, column: 13] (through reference chain: org.activiti.rest.service.api.runtime.task.TaskQueryRequest["size"])
        at org.codehaus.jackson.map.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:53)
        at org.codehaus.jackson.map.deser.StdDeserializationContext.unknownFieldException(StdDeserializationContext.java:267)
        at org.codehaus.jackson.map.deser.std.StdDeserializer.reportUnknownProperty(StdDeserializer.java:673)
        at org.codehaus.jackson.map.deser.std.StdDeserializer.handleUnknownProperty(StdDeserializer.java:659)
        at org.codehaus.jackson.map.deser.BeanDeserializer.handleUnknownProperty(BeanDeserializer.java:1365)
        at org.codehaus.jackson.map.deser.BeanDeserializer._handleUnknown(BeanDeserializer.java:725)
        at org.codehaus.jackson.map.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:703)
        at org.codehaus.jackson.map.deser.BeanDeserializer.deserialize(BeanDeserializer.java:580)
        at org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2732)
        at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1909)
        at org.restlet.ext.jackson.JacksonRepresentation.getObject(JacksonRepresentation.java:139)
        at org.restlet.ext.jackson.JacksonConverter.toObject(JacksonConverter.java:218)
        at org.restlet.service.ConverterService.toObject(ConverterService.java:161)
        at org.restlet.resource.UniformResource.toObject(UniformResource.java:647)
        at org.restlet.resource.ServerResource.doHandle(ServerResource.java:434)
        at org.restlet.resource.ServerResource.post(ServerResource.java:1114)
        at org.restlet.resource.ServerResource.doHandle(ServerResource.java:533)
        at org.restlet.resource.ServerResource.doNegotiatedHandle(ServerResource.java:590)
        at org.restlet.resource.ServerResource.doConditionalHandle(ServerResource.java:302)
        at org.restlet.resource.ServerResource.handle(ServerResource.java:849)
</blockcode>

The request works fine without the paging/sorting properties.  Example payload below.

POST: /activiti-rest/service/query/tasks
<javascript>
{
  "processInstanceVariables":
  [
    {
      "name": "orderNumber",
      "value": "11008",
      "operation": "equals",
      "type": "string"
    }
  ],
  "size" : 10,
  "start" : 0
}
</javascript>

Any ideas?
2 REPLIES 2

frederikherema1
Star Contributor
Star Contributor
Hmmm… Looks like an oversight in the REST-api object mapping. Seems that only the GET tasks?… supports paging. I'll fix this in the next release

aggiepilot04
Champ in-the-making
Champ in-the-making
Thanks.  As a workaround, I was able move the pagination/sorting parameters from the posted JSON to the URL.