Help

I am pleased to announce that we have just released Hibernate version 3.5.0-CR-1. As a refresher, Hibernate follows the JBoss versioing scheme where CR is a Candidate for Release (what many of you might call RC). The main stated goal of 3.5 is JPA 2 compliance. This is the first release we believe achieves that goal entirely. In fact we are in the process of certifying for standalone JPA 2 compliance and have integrated this CR into the imminent JBoss AS M2 release as part of their effort towards full Java EE 6 compliance.

I'll blog more about the full set of changes in 3.5 when we tag 3.5.0 final release. The changes in this CR-1 represent mostly

  • full support for derived identities (see the specification section 2.4.1 Primary Keys Corresponding to Derived Identities)
  • wrapping up various loose ends

See the release notes for all the gory details.

The distribution 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.

Once again many people helped out with this release. I'd like to specifically mention Scott Marlow who not only did some coding but provided us the invaluable, and not to be underestimated, service of performing the standalone JPA TCK runs and analyzing the results. Thanks Scott and everyone else!

7 comments:
 
13. Feb 2010, 14:44 CET | Link
Juergen Zimmermann

I found 2 issues regarding JPA 2:

a) Literal with JDBC escape syntax for date doesn't work http://opensource.atlassian.com/projects/hibernate/browse/HHH-4916

b) Keyword TYPE not supported http://opensource.atlassian.com/projects/hibernate/browse/HHH-4917

ReplyQuote
 
15. Feb 2010, 00:45 CET | Link
Domenico

Anyone can verify if this is an issue http://opensource.atlassian.com/projects/hibernate/browse/HHH-4882 ? thanks

 
16. Feb 2010, 18:37 CET | Link
Geoffrey De Smet

Keep up the good work! PS: small typo in de blog text: JBoss versioing scheme misses an n

 
17. Feb 2010, 21:15 CET | Link

That's great - I know the derived identities stuff was a total pain to implement. (Really don't know why JPA needed to grow that stuff, it seems to be just unnecessary complexity.)

 
23. Feb 2010, 12:26 CET | Link
mack

I have a working project that uses Hibernate 3.3.2 GA. I updated the project's Maven dependency to 3.5.0-CR-1, I got the new jar, but I am getting the following error:

javax.persistence.PersistenceException: No Persistence provider for EntityManager.

I don't see the org.hibernate.ejb package in this jar, but the docs on Hibernate.org indicate that the Entity Manager and Annotations are all now bundled with this single jar.

Am I missing something?

 
24. Feb 2010, 03:28 CET | Link
Fabricio Lemos | fabricio.lemos(AT)gmail.com

They are not bundled in the same jar: more details

 
03. Apr 2014, 11:13 CET | Link

In fact we are in the process of certifying for standalone JPA 2 compliance and have integrated this CR into the imminent JBoss AS M2 release as part of their effort towards full Java EE 6 compliance.

Post Comment