Specific JPA 2 related enhancements from Beta-2 include:
- Complete criteria and JPAQL support
- Full metamodel API support, including StaticMetamodel support in conjunction with the Hibernate StaticMetamodel Generator Annotation Processor.
- Initial lock support, mostly what is missing/needed is verification of all the dialects
- Mostly complete JPA 2 mapping enhancements including @Access and full Map support.
Additional enhancements from Beta-2 include:
- Expanded and more consistent read-only support
Check out the release details for the full list of changes.
The artifacts have all been published to the JBoss Maven repository. Additionally the release bundles have been uploaded to SourceForge.
Please report any issues to Jira. Visit us on IRC or the forums if you have a usage question.
A lot of effort from many folks went into this release and I'd like to thank everyone for all the bug reports, patches and development work that went into this.
Thanks!
Created: 14. Jan 2010, 12:07 CET (Steve Ebersole)
Last Modified: 24. Feb 2010, 00:32 CET (Steve Ebersole)
yeah!!! i love it!
Awesome! Almost there :-)
Thanks guys. Yeah it really is coming along nicely. A lot of the work left is what I'd call that the spec committee decide to allow; like the garbage, et al.
The criteria API turned out very nice. In fact, I think I will deprecate the Hibernate criteria api in favor of this jpa one.
Where can I find some information about generating meta model classes for criteria queries?
http://in.relation.to/Bloggers/HibernateStaticMetamodelGeneratorAnnotationProcessor ?
Congratulations! I ve just tested and I as able to change a small project that makes heavy use of the new Criteria API from EclipseLink to this new Hibernate version flawlessly. Although I do like the new Criteria API, I prefer using Strings (or even the dynamic meta model) instead of the Static Meta Model.
You have a wrong date on the home page:
02.11.2009 - Hibernate Core 3.5.0-Beta-3
Curious. I think the StaticMetamodel is one of the real beauties here, especially as IDEs begin to support this better and better and keep it up to date for you for code completion.
Hmm, someone must have fixed it already. Its correct now...
And what is wrong with EclipseLink? They have already released a version with full JPA 2.0.
One point of confusion: the docs for Annotations and EntityManager (https://www.hibernate.org/397.html) say
But this isn't true? The hibernate-core-3.5.0-Beta-3.jar artifact at http://repository.jboss.com/maven2 doesn't contain the org.hibernate.annotation package. I still need a dependency on hibernate-annotations-3.5.0-Beta-3.jar...
So what does it mean, Annotations is part of Core ??
It means that they now live in the same SVN project, now share the same release cycle, use the same version numbers and get bundled into the same release bundle (the stuff available from SourceForge). Hibernate Core aims to be modular to isolate dependencies as much as possible in terms of transitive dependencies for your projects. Hibernate Core has quite a few jars.
thanks for share this information