Hi,
I try to answer your questions from my point of view: On 13.09.13 15:18, "Marcel Bruch" <[email protected]> wrote: >The documentation is low, website falls short on any details and >examples. But maybe I missed some existing parts? I have to admit that currently the documentation is not great. But I want to add some HowTo/Docu this week and there exists also an issue (https://issues.apache.org/jira/browse/OLINGO-4) of another contributor. So I think there will be soon more documentation on the website. >The project needs to show an early prototype in a month. So the most >important question to me are: >* How usable is Olingo? In current state the Olingo OData library is usable for common read/write scenarios. The direct JPA support seems also good, but I have to admit that I did not used it by myself ;o) Unfortunately we currently have no released stable version, however I do not think that there will be any API changes between the current SNAPSHOT and the final '1.0.x' version. So IMHO you can start with the current SNAPSHOT build. >* Given the restricted timeframe, am I better off with pure JAX-RS ATM? >* How much pain is it to build something like a, say, blog platform which >OData (with posts, comments, ratings, votes, user profiles etc.)? IMHO I would give Olingo/OData a try, because with your example of a blog platform you should be in the scope of common read/write scenarios and with the JPA processor you should be able to provide easily from your database. > > >Thanks for your personal judgement >Marcel As mentioned before, this is my 'personal judgement'. More opinions are always welcome ;o) Kind regards, Michael
