On 1/30/07, Elias Torres <[EMAIL PROTECTED]> wrote:
On 1/30/07, Dave <[EMAIL PROTECTED]> wrote:
> On 1/29/07, Elias Torres <[EMAIL PROTECTED]> wrote:
> JPA does have several advantages over iBatis from my point of view.
> First, it's a Java standard API with multiple implementations
> supported Oracle, BEA, Sun, etc. Second, there is a Hibernate
> implementation of JPA, so folks can conceivably continue to use
> Hibernate if they want to. And third, for my work I have to support a
> JPA back-end. So if the Roller team picks iBatis, I'll be forced to
> maintain a second back-end -- not something I want to do.
Oh boy. So on your end, it must be JPA?
Currently that is the case. Of course, if the community decides on
Batis, that may become an untenable position.
> As much as I hate the idea, if different members of the community
> really want/need different back-end implementations, then I think we
> have figure out how to enable that or not. We come back to Craig's
> question, how to we let them co-exist. I think there are at least
> these issues:
>
> 1) Multiple back-end with equal standing. Developers must commit
> changes and get tests passing in both back-ends before committing.
>
> 2) Multiple back-ends but only one is primary. One back-end is
> designated the primary back-end and developers must ensure only that
> test pass in that primary back-end before committing.
>
> 3) One back-end allowed in SVN. Only one back-end is allowed in trunk
> and anybody who
> wants some other backend will have to maintain it separately.
I'm certain that our intentions are not to make the Roller development
by maintaining multiple back-end implementations, but we want to know
what really makes JPA the best choice. So far the
multiple-implementations story doesn't convince me. All we need is one
that works with the different dbs and it's easy to use. The simpler
the better.
I agree. Let's let others respond, but I think the best course of
action is to start the roller_4.0 branch (I plan to do that tomorrow)
and get JPA and iBatis working there as quickly as possible so we can
compare.
- Dave
