Tags
Authors
This has come up a few times so I thought I'd write up the ways to handle multi-tenancy in Hibernate. This is not an exhaustive list. We wont go into database vendor specific features (Oracle VPD, etc) for example. Generally speaking there are 3 ways to factor multi-tenancy into your database design:
Hibernate + Gradle Pointers
The Hibernate team is proud to announce the release of 3.6.0.Final. Lot of stuff has been going on.
In Hibernate there is a particular branch of logic where we need to parse and validate an org.xml.sax.InputSource that might represent either a Hibernate mapping (hbm.xml) file, a 1.0-compliant orm.xml file or a 2.0-compliant orm.xml file. Now currently Hibernate mapping files are defined by a DTD and both versions of the orm.xml files by an XSD. Currently the code builds a SAXReader with DTD and Schema validation enabled and tries to read in the source. It first maps Schema validation to the 2.0 version of the XSD; if an error occurs it then tries re-parsing mapping Schema validation to 1.0 version of the XSD.
Hibernate 3.6.0.Beta4 has been released incorporating mostly minor bugfixes and improvements. Most of the work this cycle went into the improved documentation. For those not aware we are planning on splitting the documentation into 2 books:
Deprecated CGLIB support
Kind of knew people would ask about this... So why did we decide to deprecate CGLIB support in Hibernate? First I want to point out that Hibernate and CGLIB have a very long history (and a largely good history) in terms of working together. This is not an indictment against any of the CGLIB developers. They are good guys and as I stated above for many years Hibernate and CGLIB have worked well together.
Today we have released both 3.5.5 and 3.6.0.Beta3.
The Hibernate team is happy to announce the availability of both the 3.5.4 and 3.6.0.Beta1 releases.
