I am not sure I follow the second solution but I think I probably created the issue too specific (to JPA). In general I think it should be a configuration at the service level which should then be respected by the (JPA and others) providers.
Carl On Wed, Nov 27, 2013 at 8:35 AM, V.A, Chandan <[email protected]> wrote: > Hello All, > Before solving the issue I would like to discuss the topic as mentioned in > https://issues.apache.org/jira/browse/OLINGO-27. > > I can think of two solutions > > 1) Add new property to OData JPA Context namely maxResults to control > server side paging. > > 2) Do you think will it really help in defining a new configuration > object that carries static configuration about an OData service. The > configuration object can be added to the OData Context (OData JPA context). > > Few static configuration parameters I could think > > 1) Server side Paging > > 2) Mapping Model > > 3) ... > > Any comments? > > Thanks, > Kind Regards > Chandan VA > > -- Carl J. Mosca
