Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Now, with the advent of JPA 2.0 and all the new features that come with it and that were initially missing in JPA 1.0 (<a href="http://en.wikibooks.org/wiki/Java_Persistence/What_is_new_in_JPA_2.0%3F" rel="nofollow noreferrer">http://en.wikibooks.org/wiki/Java_Persistence/What_is_new_in_JPA_2.0%3F</a>), I wonder if there is still a need to use Hibernate directly.</p> </blockquote> <p>Even for JPA 1.0, I would recommend a different approach: "JPA where you can, Hibernate where you must". </p> <blockquote> <p>What's your opinion? What's left in Hibernate 3.5 that I can't do with JPA 2.0 ?</p> </blockquote> <p>JPA 2.0 is very rich and I consider it as a huge improvement and many things that were requiring to use proprietary extensions are now standardized (see <a href="https://stackoverflow.com/questions/2435253/a-concise-clear-list-of-what-is-new-in-jpa2/2440516#2440516">this previous answer</a>). </p> <p>But you might still need some Hibernate specific extensions in some situations: a custom <code>UserType</code>, a non standard generator, a query by example, <code>@Formula</code>, <code>@Index</code>, etc. Have a look at the <a href="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html_single/#entity-hibspec" rel="nofollow noreferrer">Section 2.4, “Hibernate Annotation Extensions”</a> for more "examples".</p> <p>But let me insist, I recommend to use JPA where you can, Hibernate where you must (the later part getting thiner with JPA 2.0).</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload