Help

In terms of JPA 2, its really easier to start talking about things not yet implemented :) The set of missing features are defined by the unresolved subtasks of the following 2 Jira issues:

The still-to-be-implemented features are mainly certain aspects of derived identity support and support for embeddables with associations.

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.

As always, please report any issues to Jira and come visit us on IRC or the forums if you have a usage question.

We are getting so close folks! Great work.

4 comments:
 
30. Jan 2010, 02:29 CET | Link
William

Congratulations to the Hibernate team,

6 days, 4 hours, 39 minutes is very fast to implement the whole JPA 2 support :)

ReplyQuote
 
30. Jan 2010, 09:33 CET | Link
William wrote on Jan 29, 2010 20:29:
Congratulations to the Hibernate team, 6 days, 4 hours, 39 minutes is very fast to implement the whole JPA 2 support :)

You forgot to add the 2 together, which makes it closer to 7.5 days! ;) I think these tasks/subtasks did not account for the bulk of my criteria api work. Plus not all the developers use time tracking (its automatic for those of us using intellij and the wonderful atlassian ide plugin).

 
05. Feb 2010, 23:22 CET | Link
Fabio

why not solve all the bugs and issues in Hibernate 3.3 before thinking about JPA2?

 
12. Feb 2010, 15:57 CET | Link
jkronegg
Fabio wrote on Feb 05, 2010 17:22:
why not solve all the bugs and issues in Hibernate 3.3 before thinking about JPA2?

At least some of Hibernate 3.3 issues are solved directly in 3.5. e.g. see HHH-4905

Post Comment