Dave wrote: > Drat. I hit the send button too soon. > > How about this: since we are basically done with Roller 4.0 features > and we probably won't be adding any more, let's make the switch to the > roller_4.0_newbackend branch now. > > svn mv trunk branches/roller_4.0_oldbackend > svn mv branches/roller_4.0_newbackend trunk > > We'll make JPA the default back-end but we'll keep Hibernate in place > so that you can use it if you need to do any deployments or builds. > I'll set up my build servers to test both the Hibernate and JPA > implementations. And you can work exclusively in Hibernate if you wish > and I'll take the JPA side, as we are doing now but in one branch > instead of two. > > That will make it easy for folks (like Elias) to test JPA, easy for me > to deploy JPA and will eliminate the dreadful merge work that is > making the new installer and DI work a pain in the you know what. We > could even make some early access builds available so others can help > with testing -- we need a lot more testing this time because of > Struts2 and JPA. > > The irritating double implementation business will only exist for a > relatively short time: until we have enough confidence in JPA to > delete Hibernate from SVN. > > Could that work? > > - Dave >
I'm ok with the double impl for a bit. I'll try to find some time to test the new implementation. ... and yes don't wait for IBM to get through lawyers to give the iBatis backend for comparison. I'll say it again, if the performance is good/better than Hibernate we'd rather not raise any obstacles for Roller's progress. -Elias
