Re: [Springframework-developer] Patch to support Hibernate3 - How to provide it?

[<jue...@we...>]

As long as there isn't at least a Hibernate3 beta release, we won't ship =
any integration classes for it in the Spring distribution. We can =
certainly include some in the sandbox for the time being, but I'd still =
prefer waiting for an official beta, as alpha snapshots probably have a =
still moving API.
=20
It's a bit of a pity that they're changing package names again. =
Hibernate 1 had cirrus.*, IIRC, so each major version introduced a =
different package name. Concrete applications can be migrated easily by =
a simple search and replace, but application frameworks have to support =
both for a while (needing to duplicate their support code).
=20
That sort of thing doesn't happen with a standardized API in the javax.* =
namespace ;-)
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Colin Sampaleanu
Gesendet: Do 08.07.2004 21:04
An: spr...@li...
Betreff: Re: [Springframework-developer] Patch to support Hibernate3 - =
How to provide it?



Personally, I have not tried the dev. branch of Hibernate 3 yet, but if
they have moved to a completely separate package structure, my feeling
is that in fact mirroring the existing Hibernate 2.1 support is probably
the only viable option. People will be using Hibernate 2.1 for quite a
while, almost certainly for some time evern after Hibernate 3 is out, so
we need a solution that allows Spring to work with both versions.

W/regards to how appropriate it is to add this to Spring now, it's
probably a matter of how usable the Hibernate 3 code is. In worst case,
this could go into the sandbox.

Regards,
Colin


Oliver Geisser wrote:

> Hi.
>
> We would like to use Spring with Hibernate3 which is
> currently under development.
>
> In case you don't know: Hibernate3 is not (will not be) source-code
> compatible with Hibernate2. The biggest difference
> is the package renaming: net.sf.hibernate.* -> org.hibernate.*
>
> They also changed some Exceptions from java.lang.Class constructor
> parameters to java.lang.String parameters.
>
> This is caused by the fact that Hibernate3 isn't restricted to map
> only Java classes but can also map "dynamic-classes". So the
> identifier for a specific mapping changed from the java class to a
> string.
>
> We developed a patch to Spring which is backward compatible so you can
> use Spring with Hibernate2 or with Hibernate3.
>
> To make this work we "mirrored" the org.springframework.orm.hibernate
> package to org.springframework.orm.hibernate3. There was also the need
> to change the two exception in the org.springframework.orm package.
>
> We also mirrored the tests and all tests are ok.
>
> We would like to provide a patch but we don't know what is the =
prefered
> way to do this?
>
>
> Thanks, Olli
>
> --og





-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer