To identify the version of Hibernate ORM at runtime
by Sanne Grinovero
All,
it looks like people get easily confused by which version of ORM is
compatible with - for example - Hibernate Search.
The expected versions are documented plenty, in readme, project
sources, documentation and we even remind about the expectations
frequently in blog posts.
Wondering if it would be more effective to have some marker in ORM, to
validate at least for most critical known incompatibilities at
runtime?
I realize there is no 100% foolproof in any possible solution, but
providing a nice error message to 90% of these cases could be helpful
to a large population already, and doesn't seem too complex for us to
do.
I guess it could be simple enough to use the existing org.hibernate.Version ?
Or we could improve on those methods, if not actually adding some easy
to consume resource in the orm jars.
WDYT?
Sanne
- https://hibernate.atlassian.net/browse/HSEARCH-1816
- http://stackoverflow.com/questions/28736785/org-hibernate-impl-sessionimp...
9 years, 8 months
- 3
- 9
Bug fixes around JP-QL and more: Hibernate OGM 4.1.2 released
by Gunnar Morling
Hi,
It’s my pleasure to announce the release of Hibernate OGM 4.1.2!
This maintenance release fixes several bugs, e.g. around JP-QL, using
Hibernate OGM within SAAS environments and mapping byte[] properties on
CouchDB. We also clarified several issues in the reference guide.
Please check out the release announcement for the details [1].
--Gunnar
[1]
http://in.relation.to/Bloggers/BugFixesAroundJPQLAndMoreHibernateOGM412Re...
9 years, 8 months
- 1
- 0