bildwelt
E2E FORUM
E2E Bridge E2E Commerce

Reply To: RESTful HTTP Service & Persistent State Objects

E2E Forum Modeling & Development RESTful HTTP Service & Persistent State Objects Reply To: RESTful HTTP Service & Persistent State Objects

#793

Cliff Faurer
Participant

Hi Marcel,

The question is not so much on parsing the parameters but rather what is the recommended way to model handling a query that involves date types with gt, gte, lt, lte? And how to handle attribute filtering?

The Persistent State Adapter identifierCondition requires an explicit logical date expression. How to handle a RESTful request like the following:

curl -X GET -G “http://localhost:12007/ticket?status=Submitted&creationDate.gt=2014-02-04T21:08:00.889767Z&creationDate.lte=2014-02-04T21:10:10.889767Z”

The ticket resource has several date field that can be queried in this way; creationDate, targetResolutionDate, statusChangeDate and resolutionDate.

The second question is about how to filter the returned attributes for a request like the following:

curl -X GET -G “http://localhost:12007/ticket?fields=status,description&status=Submitted”

Only the status and descriptions fields for every created ticket should be returned.

Thanks,

Cliff