Hello Aparna, Yes, the Java Annotation Extension can only be used as “none persistent in-memory datastore”. Because it started as PoC and the adaption for other data stores is currently not under development by the olingo community (see: https://issues.apache.org/jira/browse/OLINGO-129 <https://issues.apache.org/jira/browse/OLINGO-129>).
Based on that we do not recommend to use the Java Annotation Extension in a productive environment. Best Regards, Michael > On 07 Sep 2015, at 15:37, Khare, Aparna <[email protected]> wrote: > > Dear Colleagues, > > In the latest release 2.0.4 (olingo Odata v2) We further noticed that > AnnotationServiceFactory is tied to in-memory Data Source and ListProcessor > and AnnotationEDMProvider are not exposed externally which could have been > used to create our own ODATA service from annotations. > > Please lets us know how we can use the Annotation based ODATA service > productively. > > Thanks in Advance, > Aparna > > -----Original Message----- > From: Khare, Aparna [mailto:[email protected]] > Sent: Monday, September 7, 2015 5:44 PM > To: [email protected] > Subject: AnnotationProcessor in Olingo > > > Dear Colleagues, > > Can you please guide whether Annotation Processors can be used for > productive code base and which version I can use in my code, > From my earlier interactions I remember that I was not productive. Also we > may need all the Odata operation support like $select,order etc. > > Thanks , > Aparna >
smime.p7s
Description: S/MIME cryptographic signature
