[jira] [Commented] (OLINGO-549) POC: ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510335#comment-15510335 ] Alexandre Desjardins commented on OLINGO-549: - Thank you [~chrisam]. I have subscribed to the mailing list. We will keep a close eye on how things develop. I doubt my Boss will allow me to spend time on the project unfortunately, I might try to check it on my personal time. Thank you again for the clarifications. > POC: ODataV4 JPA Processor > -- > > Key: OLINGO-549 > URL: https://issues.apache.org/jira/browse/OLINGO-549 > Project: Olingo > Issue Type: New Feature > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A > > A proof of Concept for transforming JPA models into OData V4 compliant EDM > models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 > specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-549) POC: ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510076#comment-15510076 ] Christian Amend commented on OLINGO-549: [~jemag] I don`t know how this develops and how the implementation will take place at this point in time. I have started a discussion on the dev mailing list (dev@olingo.apache.org) on how to best integrate the code into Olingo. If you like you can subscribe to this list (dev-subscr...@olingo.apache.org) and take part in this discussion. My very personal opinion is that you should not expect a stable JPA release within this or next month. I think that it would be best to make an alpha release first to see how the code behaves and if there is interest from the community e.g. other contributors. I personally will invest time to integrate this into the project, setting up releases or guiding discussion regarding OData questions. I don`t think I will have time to actually implement features or bug fixes for the JPA extension. If you would like to get involved here you could make certain that the project is going into the right direction :) > POC: ODataV4 JPA Processor > -- > > Key: OLINGO-549 > URL: https://issues.apache.org/jira/browse/OLINGO-549 > Project: Olingo > Issue Type: New Feature > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A > > A proof of Concept for transforming JPA models into OData V4 compliant EDM > models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 > specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-549) POC: ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509963#comment-15509963 ] Alexandre Desjardins commented on OLINGO-549: - [~chrisam]thank you very much for your reply. My main concern is that we invest time into implementing Olingo with this JPA processor, only for the processor to be scrapped a few weeks/months down the line (or not maintained). Is there any chance that this JPA processor could eventually be adopted as an official component of Olingo ? (So that we can be sure that there will be a minimum development/ maintenance) If so, how long would it take for the JPA processor to receive semi-official approval? Sorry about all the questions, our small team is currently at a crossroad and we want to make sure that we invest our time judiciously with a transition to Olingo. (I'll try to take a quick look at this jpa processor solution on my off hours). > POC: ODataV4 JPA Processor > -- > > Key: OLINGO-549 > URL: https://issues.apache.org/jira/browse/OLINGO-549 > Project: Olingo > Issue Type: New Feature > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A > > A proof of Concept for transforming JPA models into OData V4 compliant EDM > models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 > specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-549) POC: ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509124#comment-15509124 ] Christian Amend commented on OLINGO-549: [~jemag] there has been another contribution with this JIRA issue: https://issues.apache.org/jira/browse/OLINGO-1010 Apparently it is a first working JPA solution. I intended to look at it this week and see how we can integrate it into Olingo. If you have any feedback regarding the contribution please let us know. My JPA knowledge is not the best :) > POC: ODataV4 JPA Processor > -- > > Key: OLINGO-549 > URL: https://issues.apache.org/jira/browse/OLINGO-549 > Project: Olingo > Issue Type: New Feature > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A > > A proof of Concept for transforming JPA models into OData V4 compliant EDM > models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 > specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-549) POC: ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508295#comment-15508295 ] Alexandre Desjardins commented on OLINGO-549: - Is the JPA Processor for OData V4 still in development? If so, is there any rough timeline? [~chandan.v.a] We want to use Olingo, but if there is no JPA processor under way, it would definitely make things more difficult for our small team... > POC: ODataV4 JPA Processor > -- > > Key: OLINGO-549 > URL: https://issues.apache.org/jira/browse/OLINGO-549 > Project: Olingo > Issue Type: New Feature > Components: odata4-JPA >Affects Versions: (JPA) V4 4.0.0-beta-01 >Reporter: Chandan V.A > > A proof of Concept for transforming JPA models into OData V4 compliant EDM > models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 > specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-549) POC: ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323704#comment-14323704 ] Chandan V.A commented on OLINGO-549: Hello Karuna, JPA extension for OData V4 is planned to be done in a phased manner. Tentative timeline with minimal capability can be seen sometime before May 2015 end. Regards Chandan POC: ODataV4 JPA Processor -- Key: OLINGO-549 URL: https://issues.apache.org/jira/browse/OLINGO-549 Project: Olingo Issue Type: New Feature Components: odata4-JPA Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A A proof of Concept for transforming JPA models into OData V4 compliant EDM models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-549) POC: ODataV4 JPA Processor
[ https://issues.apache.org/jira/browse/OLINGO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318678#comment-14318678 ] Karuna Joshi commented on OLINGO-549: - What is the approximate time we can expect first release for JPA support ? POC: ODataV4 JPA Processor -- Key: OLINGO-549 URL: https://issues.apache.org/jira/browse/OLINGO-549 Project: Olingo Issue Type: New Feature Components: odata4-JPA Affects Versions: (JPA) V4 4.0.0-beta-01 Reporter: Chandan V.A Assignee: Chandan V.A A proof of Concept for transforming JPA models into OData V4 compliant EDM models and supporting OData V4 protocol compliant operations into JPA 2.0/2.1 specific operations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
