For tutorial the reference scenario is maybe too complex. The reference scenario is all what you can do with the library and we are using it for testing. The samples (not just one) should have hello world character and point out only features of the library.
Stephan On 12.09.13 09:22, "Amend, Christian" <[email protected]> wrote: >HI, > >how would these tutorials be different from the Reference Scenario? > >Imho we should use our existing scenario and build the tutorials based on >that. Otherwise I fear we introduce tutorials which have only a little >value but have to be maintained with a lot of effort. > >Best Regards, >Christian > >-----Original Message----- >From: Bolz, Michael [mailto:[email protected]] >Sent: Mittwoch, 11. September 2013 14:59 >To: [email protected] >Subject: Project Structure / Tutorial Module > >Hi, > >after I have noticed "https://issues.apache.org/jira/browse/OLINGO-4"; I >thought about writing a small quick starter How-To/Tutorial with a sample >project. >I would add this sample as {{maven module}} but I would not mess up our >complete project structure. >Hence, I suggest to group/sort our current project a little bit so that >it will keep clear. >Below is my recommendation for a structure: > >org.apache.olingo.odata2-parent >-> org.apache.olingo.odata2-processor.jpa > --> org.apache.olingo.odata2-jpa.processor.api > --> org.apache.olingo.odata2-jpa.processor.core >-> org.apache.olingo.odata2-lib > --> org.apache.olingo.odata2-api > --> org.apache.olingo.odata2-core > --> org.apache.olingo.odata2-testutil > --> org.apache.olingo.odata2-fit > --> org.apache.olingo.odata2-ref > --> org.apache.olingo.odata2-ref.web >-> org.apache.olingo.odata2-samples > --> org.apache.olingo.odata2-tutorial [NEW] > --> org.apache.olingo.odata2-tutorial.web [NEW] > >What do you think? > >Kind regards, >Michael
