|
From: Colin S. <col...@ex...> - 2004-07-08 19:00:01
|
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 |