I also think that a second data model makes sense to show different use cases
--Jens -----Original Message----- From: Klevenz, Stephan [mailto:[email protected]] Sent: Donnerstag, 29. August 2013 13:36 To: [email protected] Subject: Re: distributions +1 for 3 Another data model for JPA will maybe useful to get ideas about different OData use cases. -- Stephan On 28.08.13 09:17, "V.A, Chandan" <[email protected]> wrote: >Hi, >Just a thought. Do we need a common data model for the reference >scenarios of OData Lib and JPA Lib; so it gives a common understanding of >the data model for the developers using both the library. I mean only a >common data model and not a common reference scenario implementation. > >1) Is this Ok? >2) if 1) is Ok then I can create a new reference scenario for JPA based >on the existing OData Lib reference scenario. Employee - Manager - City - >Room - Team - Location - Photo - Building. >3) if 1) is not Ok then I can push the existing reference scenario for >JPA into git. Sales Order - Sales Order Item - Notes - Materials - Store >- Storage Location. The existing reference scenario covers many concepts >from JPA 2.0 specification. > >Thanks, >Kind Regards >Chandan VA > >-----Original Message----- >From: Klevenz, Stephan [mailto:[email protected]] >Sent: Tuesday, August 27, 2013 7:42 PM >To: [email protected] >Subject: Re: distributions > >Cool ideas. I am working currently on a distribution module. Do we have >code for a JPA based reference scenario? > >Greetings, >Stephan > > >On 25.08.13 07:18, "V.A, Chandan" <[email protected]> wrote: > >>Hi, >> >>+1 for [1] and [2]. >> >>Can we also distribute >>3. Reference scenario for OData Lib >>4. Reference scenario for OData JPA Lib >> >>The reference scenario could use a specific version of dependency for >>example CXF, Eclipse Link 2.5.0 in case of JPA. >> >>Secondly >>Should we also consider separate distributions in the download page for >>A. JARs with no source code >>B. JARs + source code + java docs as one bundle >> >>In case developers don't have experience with git, then they can directly >>download the source code from the download page as .zip format. >> >> >>Thanks, >>Kind Regards >>Chandan VA >> >>-----Original Message----- >>From: Klevenz, Stephan [mailto:[email protected]] >>Sent: Friday, August 23, 2013 1:34 PM >>To: [email protected] >>Subject: distributions >> >>Hi, >> >>To get a first release we have to think about distributions which we can >>put onto a download page. >> >>Basically I do see this kinds of distributions: >> >> 1. OData Lib (api + core + dependencies) >> 2. OData Lib + JPA Processor (jpa api + jpa core + annotations + more >>dependencies) >> >>About the dependencies: >> >>I suggest not to bundle a specific Apache CXF version. The project uses a >>specific CXF version (currently 2.7.5) only for testing and the lib >>should work also with other versions. Potentially any JAX-RS >>implementation should work. >> >>WDYT? >> >>Regards, >>Stephan >
