Hibernate 3.5 was just released with JPA 2 support: http://in.relation.to/Bloggers/Hibernate350FinalRelease
We should support it as a persistence provider for JPA 2.0.
should we also replace currently bundled hibernate with new one?
I am not quite sure. One thing is that the Hibernate framework support (non-JPA style) is in maintenance mode for this release, and we should not do anything that has a risk of destabilizing it. I am not sure if the config file format has changed, or...
Next, when we support more versions, we should consider implementing a config UI in the Web Frameworks panel that allows the user to use their own version of the library (not just the bundled one), like we do for JSF.
Is there a way to support Hibernate 3.5 as a JPA 2 provider, without replacing the bundled jars?
Sorry, this is meant to be enhancement, not defect.
I'll try to find out if it can be done relatively fast to support new persitence library with new hibernate, there are some issues with persistence libraries(may affect) and some updates are required in hibernate provder.
now bundled hibernate is shown as "hibernate (jpa 1.0)" but if I create custom hibernate library from "new pu wizard" from hibernate 3.5 jars, new item "hibernate(jpa 2.0)" will appear. tried a bit in j2se and all seems ok, there is minor issue in web project in pu visual designer as hibernate (jpa1.0) is shown instead of "hibernate (jpa 2.0)" but it may have no side effect. please try to see if except this issue current support is enough.
Thanks a lot, Sergey, I will try. Another aspect of the support may be to support Hibernate's annotation processor for generating the canonical metamodel.
Integrated into 'main-golden', will be available in build *201004020200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Sergey B. Petrov <firstname.lastname@example.org>
Log: fix#183327 some part to support both hibernate jpa 1.0 and hibermnate jpa 2.0
(In reply to comment #2)
> Next, when we support more versions, we should consider implementing a config
> UI in the Web Frameworks panel that allows the user to use their own version of
> the library (not just the bundled one), like we do for JSF.
Yes. And similarly for Spring. Perhaps list of frameworks should be changed to table with two columns where second column shows version. The version would be a combo box listing all available versions including custom ones. It could also contain an option at the bottom of combo box popup "Register new library". Just an idea. It would have implications on current UI and may require too many changes though.
The hibernate 3.6.1 has release.
I tried to create a new persistence unit with Build 201105050000, but Hibernate JPA 2.0 cannot be selected. In libraries, "Hibernate JPA" still seems to be old.
Since this did not make it into NB 6.9, please change the target milestone.
(In reply to comment #11)
> Since this did not make it into NB 6.9, please change the target milestone.
I can get hibernate / jpa2 by adding the hibernate 3.6 libraries myself as in comment #5. bug 190800 is a duplicate of this one targeted at NB 7 (and still open as well). Isn't it time to bundle a more recent release of hibernate than 3.2.5?
yes, hibernate is supported as jpa2.0 provider(need to add new library) now but to bundle newer version a lot of hibernate specific(not jpa) related functionality may need to be updated (hql editor etc.)
Wow, 2 years old and no support for the latest version of Hiberate? Hibernate, the most used ORM framework?
Netbeans is the flaming pile of dog shit it's always been. Continue writing substandard garbage. It's why you're a fucking joke.
We appreciate your interest in the Hibernate support in NetBeans, but please refrain from using offensive language in comments. This is not ethical.
Netbeans 7.4 contains hibernate 3.6/JPA 2 support