OK, guys. I'm with you for JPA 1.0 and 2.0 support (+1). +1 also for small migration SQL scripts from dao-hib. Something to include here in future: https://cwiki.apache.org/confluence/display/ODExSITE/Upgrading+ODE
On Fri, Jun 11, 2010 at 6:19 AM, Milinda Pathirage < [email protected]> wrote: > +1 for providing both JPA 1.0 and JPA 2.0 support. > > Milinda > > > On Fri, Jun 11, 2010 at 6:14 AM, Jeff Yu <[email protected]> wrote: > >> I think we shouldn't expect to use the schema as same as dao-hib at this >> stage, as I believe there would still some minor changes in the JPA Dao. >> And >> I think it should be acceptable to have little update on the schema change >> as long as we specify them out and provide some simple migration utility. >> >> With regard to the JPA 2.0, I am thinking about that whether we can make >> ODE >> run against both JPA 1.0 and JPA 2.0 container. I believe we have many >> users >> running against JPA 1.0 container, if we upgrade it to JPA 2.0, they have >> to >> upgrade their JPA container. So it would be best that we say adding some >> jars, it would support JPA 2.0, otherwise, it is for JPA 1.0 by default. >> what do you think? >> >> For the jpa change that I did now, I will try to commit them in after >> axis2-war module test part is enabled and checked in. >> >> Regard >> Jeff >> >> On Fri, Jun 11, 2010 at 1:32 AM, Aaron Anderson <[email protected] >> >wrote: >> >> > HI Rafal, >> > >> > I have attached the generated derby DDL scripts for the hibernate DAO >> > (derby-hib.sql) and JPA DAO (derby.sql). They are very similar and it >> > shouldn't be much of a problem to make the JPA entities map to the >> hibernate >> > schema. It is probably best that there is one static and supported DB >> schema >> > anyway. >> > >> > While addressing the JPA changes we should also consider upgrading to >> JPA >> > 2.0. There are only a few features that would simplify the JPA code but >> if >> > there are not that many current ODE JPA users it would be best to start >> off >> > with the latest version and avoid future versioning conflicts. >> > >> > Regards, >> > >> > Aaron >> > >> > *From:* Rafal Rusin <[email protected]> >> > *To:* Jeff Yu <[email protected]>; Aaron Anderson < >> > [email protected]> >> > *Cc:* [email protected] >> > *Sent:* Thu, June 10, 2010 9:01:00 AM >> > *Subject:* Changing roadmap for JPA refactoring >> > >> > Hello, >> > >> > is this possible (and how much effort it is) to make JPA (hibernate >> powered >> > version) work on the same schema as dao-hib does? >> > This way we could migrate all current hibernate users to JPA in future >> and >> > finally drop hib-dao. I believe there are not much current OpenJPA >> users, so >> > we can modify this schema. On the other hand, there's a lot of dao-hib >> > users, >> > so we really want to migrate them (because of later drop for dao-hib). >> > >> > What do you think? >> > >> > -- >> > Regards, >> > Rafał Rusin >> > http://rrusin.blogspot.com >> > >> >> >> >> -- >> Cheers, >> Jeff Yu >> >> ---------------- >> blog: http://jeff.familyyu.net >> > > > > -- > Milinda Pathirage > Technical Lead & Product Manager WSO2 BPS; http://wso2.org/bps > WSO2 Inc.; http://wso2.com > E-mail: [email protected], [email protected] > Web: http://mpathirage.com > Blog: http://blog.mpathirage.com > -- Regards, Rafał Rusin http://rrusin.blogspot.com
