Re: Changing roadmap for JPA refactoring

2010-06-10 Thread Milinda Pathirage
+1 for providing both JPA 1.0 and JPA 2.0 support. Milinda On Fri, Jun 11, 2010 at 6:14 AM, Jeff Yu 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 acceptabl

Re: Nexus access

2010-06-10 Thread Jeff Yu
+1. Regards Jeff On Thu, Jun 10, 2010 at 10:51 PM, Tammo van Lessen wrote: > Hi devs, > > I'd like to try using Nexus for the ODE release process (nexus makes > this process apparently a lot simpler), the infra process for this > requires us do a vote so please vote +1 to doing this. > > Here is

Re: Changing roadmap for JPA refactoring

2010-06-10 Thread Jeff Yu
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.

Re: Changing roadmap for JPA refactoring

2010-06-10 Thread Aaron Anderson
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 D

Re: Nexus access

2010-06-10 Thread Paul Brown
Anything you can do to get "easy" and "release" in the same sentence (without a negative) is good by me: +1 On Jun 10, 2010, at 5:51 AM, Tammo van Lessen wrote: > Hi devs, > > I'd like to try using Nexus for the ODE release process (nexus makes > this process apparently a lot simpler), the inf

Re: Changing roadmap for JPA refactoring

2010-06-10 Thread Rafal Rusin
Great. OK, we can plan upgrade to JPA 2.0 and synchronizing schemas as soon as current work is committed into trunk. On Thu, Jun 10, 2010 at 5:32 PM, Aaron Anderson wrote: > HI Rafal, > > I have attached the generated derby DDL scripts for the hibernate DAO > (derby-hib.sql) and JPA DAO (derby.sq

Re: Nexus access

2010-06-10 Thread Kurt T Stam
+1 (non- binding) --Kurt David Carver wrote: +1 anything to make release process easy and consistent. Dave On 06/10/2010 05:51 AM, Tammo van Lessen wrote: Hi devs, I'd like to try using Nexus for the ODE release process (nexus makes this process apparently a lot simpler), the infra process f

Re: Nexus access

2010-06-10 Thread David Carver
+1 anything to make release process easy and consistent. Dave On 06/10/2010 05:51 AM, Tammo van Lessen wrote: Hi devs, I'd like to try using Nexus for the ODE release process (nexus makes this process apparently a lot simpler), the infra process for this requires us do a vote so please vote +1

Changing roadmap for JPA refactoring

2010-06-10 Thread Rafal Rusin
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

Re: Nexus access

2010-06-10 Thread Rafal Rusin
+1 from me (SMX4 OSGi will make use of it, since it has grab-from-maven-repo feature; and there was also community request for it). On Thu, Jun 10, 2010 at 2:51 PM, Tammo van Lessen wrote: > Hi devs, > > I'd like to try using Nexus for the ODE release process (nexus makes > this process apparentl

Nexus access

2010-06-10 Thread Tammo van Lessen
Hi devs, I'd like to try using Nexus for the ODE release process (nexus makes this process apparently a lot simpler), the infra process for this requires us do a vote so please vote +1 to doing this. Here is my +1. Thanks, Tammo -- Tammo van Lessen - http://www.taval.de

[ANNOUNCE] Apache ODE 1.3.4 released

2010-06-10 Thread Tammo van Lessen
The Apache ODE team is pleased to announce the release of Apache ODE 1.3.4. It includes many improvements and bug fixes. Apache ODE is a WS-BPEL compliant web services orchestration engine. It organizes web services calls following a process description written in the BPEL XML grammar. Another way