SessionFactory issue after Hibernate 4 upgrade

[burke (Burke Mamlin)]

@mogoodrich

I could see confusion if the latest versions of each module start to fail cryptically because the implementation hasn’t installed the hibernate compatibility module.

Is there an easy recipe (e.g., one-liner) we could give to module authors to include in their startup code that would fail loudly in a well-explained way? For example:

// Copy this into your module's startup code
if (/* pre-hibernate4 & no compatibility module */) {
  throw ModuleException("Hibernate compatibility module required. See http://om.rs/hibernate4");
}

We could point om.rs/hibernate4 to a wiki page summarizing the issue with instructions on how to fix it (i.e., how to install the hibernate compatibility module).