Why we use JPA annotations instead of hibernate annotations

Question

I have one POJO in my Sample Hibernate Application and that points to table in my database. In my POJO class having @Entity annotation from JPA(javax.persistence.Entity).

What is the need of importance to place JPA annotation instead of Hibernate API.

Thanks in Advance...!

what has Hibernate API got to do with anything? an annotation is an annotation not an API. Presumably the docs to the JPA implementation you have chosen would tell you the answer to that question ... — Neil Stockton, Jan 28 '15 at 13:33

score 5 · Answer 1 · edited May 23 '17 at 12:08

5

I suppose this might be an answer to your question: What are the differences between Hibernate and JPA?

Using JPA annotations you can use any JPA provider, not only Hibernate, e.g. EclipseLink.

edited May 23 '17 at 12:08

Community

1
1

answered Jan 28 '15 at 11:56

Piohen

1,514
15
23

score 1 · Answer 2 · answered Jan 28 '15 at 11:56

1

Hibernate only has annotations for its proprietary features. For standard features (like declaring that a class is an entity, specifying its table name, etc.), it relies on standard JPA annotations.

That's a good thing, because if you only use standard JPA features, you should be able to use any other JPA implementation instead of Hibernate.

answered Jan 28 '15 at 11:56

JB Nizet

678,734
91
1,224
1,255

Standard argument. Falls down though because it's very very rare to switch ORM provider in this way. I've heard of it once or twice, but only ever switching to hibernate from some other, second rate, implementation. – Software Engineer Jul 09 '16 at 01:38

score 0 · Answer 3 · answered Jan 28 '15 at 11:59

0

You use hibernate as implementation of JPA API. You should be able to change hibernate with another implementation (like EclipseLink) without changing in the code. This is why you should only use JPA annotations.

answered Jan 28 '15 at 11:59

klagrida

169
1
4

Who says that for any particular project one 'should' be able to switch out ORM provider? This argument simply isn't relevant to most projects as almost nobody ever switches away from hibernate. – Software Engineer Jul 09 '16 at 01:37

score 0 · Answer 4 · edited Jul 09 '16 at 01:34

0

The advantage of using JPA annotation is JPA is an Oracle Java standard , it is always good to use a standards. What if tomorrow hibernate is no longer popular and another other ORM tool is coming up?

edited Jul 09 '16 at 01:34

Software Engineer

15,457
7
74
102

answered Jul 06 '16 at 22:19

Dapper Dan

932
11
23

It is not 'always' good to use standards -- that's nonsense. – Software Engineer Jul 09 '16 at 01:34

score 0 · Answer 5 · answered Jul 09 '16 at 01:41

The real argument for using JPA is that most java developers will understand what you've written. Arguments suggesting that you may switch out provider/ORM are meaningless to most projects as this almost never happens. But, your code is probably going to be read by many different developers over its lifetime, and it would be good if you've used tools and techniques they already know, rather than some library nobody has ever heard of. In this case, JPA allows you to communicate with the future a lot more easily than the original hibernate annotations.

Why we use JPA annotations instead of hibernate annotations

5 Answers5