[Springframework-developer] Re: Hibernate 3

[Artur K. <kar...@as...>]

Colin Sampaleanu wrote:

> Hibernate 3 is now out in Alpha. We should probably start thinking about
> how to add support for it, and a timeframe.

It would be great to have HB3 incorporated into spring, even in sandbox. Lot
of people could possibly help testing HB3 (well, at leas me:). Of course
HB3 has a lot of new, shiny, sexy features :).
 
> It's actually good that we didn't do anything before this, as there have
> been 4-5 bug fixes in Hibernate related session handling and transaction
> code the last few weeks. Since Hibernate 3 is in an entirely different
> package, what I think is probably the only viable option given that
> people are going to be using Hibernate2 for a long time yet, is to build
> up a parallel hierarchy of the support classes, probably with the same
> package names, but 'hibernate3' instead of just 'hibernate'. Arguably,
> the class names might make sense to have the version too, since it would
> reduce confusion a lot.

I'm not convinced. I thing most developers will switch from 2 to 3 within a
year. After that HB2 will be virtually outdated (like HB1 is now) and
spring will end up with "polluted" package names. I tend to wait few months
and switch completly to HB3, instead of HB2 and not "polluting" spring
packages. What about using "old" *.hibernate.* packages and adding classes
with version suffix? Just my $0.02. (and of course, with CVS there are,
unfortunatelly serious problems with directories - so refactoring (future
hibernate3->hibernate migration) is rather hard, in this case).

> In terms of a timeframe, this could happen at any time in the sandbox,
> and probably in the main source tree after 1.1 final is out. The main
> issue is developer time, although I see the work as being pretty
> straightforward to do a direct translation. It's definitely worth it to
> then figure out what makes sense to add given the enhanced capabilities.
> 
> One interesting thing I read in the release notes; Hibernate now throws
> unchecked exceptions instead of checked exceptions...

Other which could reflect spring API are "named-entities". All "old" session
- entity related - methods are now doubled with new, overloaded versions
with entity name.

Having support for new hibernate - spring managed - events would be cool
also.

Artur