Update to Hibernate 3.6

[Nicklas Nordborg]

I don't know when this will happen. Considering that Hibernate 3.5 was just released it is probably some time before this happens. The reason that I add this ticket now is that the Hibernate team is redesigning the type system and it is important that we don't miss this when we update to Hibernate 3.6.

The redesign started in Hibernate 3.5.2 which deprecated several classes/methods/constants (see #1488). This caused some issues in the BASE API and will require more changes once BASE is updated to use Hibernate 3.6.

• Type.getHibernateType() should be removed
• VirtualColumn.getType() should be removed
• TypeWrapper needs to be fixed since the use of NullableType no longer will work.
• Metadata.getPropertyPath() needs to be fixed since the use of ImmutableType no longer will work.

There are possible other issues that I am not aware of now or that may show up later if there are additional changes in the Hibernate code.

[Nicklas Nordborg]

(In [5475]) References #1489: Update to Hibernate 3.6

• Added the 3.6 hibernate3.jar and changed some other jar files.

• Removed deprecated methods in Type and VirtualColumn.

• Some other code changes due to changes in the Hibernate type system.

• And some code changes in HibernateUtil.init1() and init2() methods due to changes in how the hibernate configuration works. I am not completely comfortable with our vulnerability to the inner workings of Hibernate.

I would like to get rid of our manipulation of PersistentClass objects. It would be better to make our changes to the XML mapping files before we pass them on to Hibernate. But I'll add that as another ticket since, strictly speaking, it has nothing to do with this update.

[Nicklas Nordborg]

(In [5476]) References #1489: Update to Hibernate 3.6

Changed URL:s to DTD:s used in various Hibernate mappings files as described in ​http://opensource.atlassian.com/projects/hibernate/browse/HHH-5485

[Nicklas Nordborg]

(In [5560]) Fixes #1489: Update to Hibernate 3.6

Added information about the removed methods in the documentation.