Hi Hanif,
Question can be posted here or created as issue in JIRA (https://issues.apache.org/jira/browse/OLINGO) with issue type ³Question². Now to your questions: > - Is this class meant to be used as a base class that one can extend but >override as needed? It is not intended that the ListsProcessor is extended > - I really like the DataSource abstraction interface but noticed there >is no overloaded method for readData() that takes in say a Filter >expression so that I could apply the filter in conjunction with >retrieving the data using some data service. I guess this goes back to >the above point about retrieving the data in its entirety and then post >filtering. as well as it is not intended that the DataSource interface is extended. Only classes/interfaces in an API module are intended (supported) to be extended. But their exists ideas to move/migrate above mentioned interfaces to the API. But this would be a bigger change and should be well discussed. To answer your other questions I have to take a deeper look into the project. Kind regards Michael On 24/02/14 15:21, "Rajabali, Hanif" <hanif.rajab...@sap.com> wrote: >Friendly bump in case it got lost :) Should questions be posted to this >list or is there another more appropriate means? >Thanks! >Hanif > >-----Original Message----- >From: Rajabali, Hanif [mailto:hanif.rajab...@sap.com] >Sent: Thursday, February 20, 2014 12:34 PM >To: dev@olingo.incubator.apache.org >Cc: Xu, Yao Feng; Bhattacharyya, Rana >Subject: Using ListsProcessor as base class but need to override some >functionality > >Hi community, I recently came across the ListsProcessor as part of the >1.1 release and found it great in that it provides all the boiler plate >code necessary to fulfill all of the necessary requirements of the >processor. I have several questions: >- Is this class meant to be used as a base class that one can extend but >override as needed? >- in the readEntitySet() method, it firsts retrieves all of the data and >then applies system query options. In my case, I have a service which >takes in a wild card expression. My filter query looks like this; >$filter=MyField eq '1'. My service will treat that '1' as a wild card >and only return results that begin with '1'. So in this case, I want >to retrieve that subset of data first (through an implementation of the >ExpressionVisitor) and then apply the other system options to it like >$top, $skip etc.... So I can override the readEntitySet() method but I'd >like to reuse convenience methods like getStructuralTypeValueMap() or >getCallbacks() which are all private instead of protected in the >ListsProcessor instead of having to copy them into my child class. Am >I extending the right class? Also, what if my backend was a database >and I wanted to use the system query options to directly translate into a >db query that takes into account things like $top? It wouldn't make >sense to retrieve the entire set first and then apply post filtering no? >- I really like the DataSource abstraction interface but noticed there is >no overloaded method for readData() that takes in say a Filter expression >so that I could apply the filter in conjunction with retrieving the data >using some data service. I guess this goes back to the above point >about retrieving the data in its entirety and then post filtering. >- Also, I'm a big fan of Spring and try and use it for DI and bean >management (also for unit testing purposes) but its hard to do given the >way the things are initialized..... any thoughts on the best way to >leverage Spring with the Olingo library? > >I'm sure there is good reason for what is there now and I've probably >missed something or am taking the wrong approach... I beseech this great >community for help and bow in utter humility. > >Thank you! >Hanif
smime.p7s
Description: S/MIME cryptographic signature
