On 8/16/06, Anil Gangolli <[EMAIL PROTECTED]> wrote:
I support Elias's option #2 with some concessions to #1.
I feel about the same way. On the question of "who here wants to replace Hibernate?" Hibernate's LGPL licensing is incompatible with Apache policy and there exists a set of contributors who are willing and able to provide an alternative backend impl. I'm a member of that set. If we create an alternative, it works well and we've got consensus then we'll ship it with Roller. Do we have to do this before we graduate? I sure as hell hope not. On the question of "which ORM should we choose?" I definitely believe we should ship one ORM with Roller and the Roller project should not do anything to promote, document or support the idea of users plugging in alternative ORMs. Personally I favor JPA because 1) there will be multiple high-quality implementatons (some at Apache) and 2) Hibernate is one of the implementations. So we'd ship OpenJPA or something similar, but folks who *really* want to continue using Hibernate can figure out on their own how to configure Roller to use Hibernate's JPA implementation. On the question of "Data Mapper good or bad?" I'm +1 on Data Mapper. The Data Mapper pattern allows us to abstract ORM queries, just as our Persistence Strategy allows us to abstract ORM load/save operations. We'll have a complete persistence abstraction, something I've always wanted to see. The ability to compare JPA, JDO and possibly other ORMs seems like a key feature right now. Having named and externalized queries is nice too. - Dave
