Hi Martin, Nice to see your interest in OData and especially in Olingo ;o)
> I see that there are 2 commits done for olingo-549 (the odata4-jpa jira > issue): > https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=shortlog;h=refs/heads/OLINGO-549-ODataV4-JPA > > <https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=shortlog;h=refs/heads/OLINGO-549-ODataV4-JPA> > Has any other work been done already on odata4-jpa, which I can use/build > further on? And your interest in the JPA extension. > Are there ideas to do major restructure of the jpa code going from odata2 to > odata4, or other changes/insights for the odata2 code moving to odata4? > How much/what parts of the odata2-jpa code can be re-used for odata4? Because I’am myself not so familiar with the JPA extension in Olingo V2 I can not answer those questions. However, probably Chandan could answer this and/or support you with the first steps around JPA extension in Olingo V4. From my side I can offer that if you want to contribute into the "OLINGO-549-ODataV4-JPA" branch I can assist you. Best Regards, Michael > > Looking forward to work on this and any comments/input you may have! > > Thanks > > gr. Martin > > -- > > With Regards, Martin Taal > > Springsite/Elver.org > Office: Hardwareweg 4, 3821 BV Amersfoort > Postal: Nassaulaan 7, 3941 EC Doorn > The Netherlands > Cell: +31 (0)6 288 48 943 > Tel: +31 (0)84 420 2397 > Fax: +31 (0)84 225 9307 > Mail: [email protected] - [email protected] > Web: www.springsite.com - www.elver.org >
smime.p7s
Description: S/MIME cryptographic signature
