Here is a proposition regarding the Hibernate issue: we have both an
in-memory and a persistent implementation. We can do our first release only
with the in-memory one. That won't block us and hopefully by the time we're
ready for a second or third release this will be out of our way.

What do you think?

On 9/6/06, Alex Boisvert <[EMAIL PROTECTED]> wrote:

Paul Brown wrote:
>> Let's not make Hibernate an obstacle to a regular release schedule.
>
> So, what's the best choice?  OpenJPA?  iBatis?  From what I remember
> of the entity model, it's straightforward, and iBatis might be a good
> candidate.
>

I believe Lance started looking into OpenJPA.

alex

Reply via email to