Hibernate vs JPA (ORM techniques) - Dubious concept

I am going through the OR Mapping frameworks. I got the the purpose of using Hibernate and JPA that is to achieve ORM, then what is difference between them?
I read somewhere that JPA is a standard Specification while Hibernate is an Implementation, What is specification and implementation? any real time example.

I read somewhere that JPA is a standard Specification while Hibernate is an Implementation

This is correct. A specification is a plan or blueprint of something, the implementation is that actual thing.

Paul Sturrock wrote:

I read somewhere that JPA is a standard Specification while Hibernate is an Implementation

This is correct. A specification is a plan or blueprint of something, the implementation is that actual thing.

So would you please define in detail , The other implementations of JPA other than Hibernate?

The easiest way to do that is to look here: JPA implementation.

Paul Sturrock wrote:The easiest way to do that is to look here: JPA implementation.

Dts very nice suggestion. Hence, One more suggestion is required. What prerequisites are needed to start learning Hibernate? I mean what basics are required.
and also mention the hibernate book for very beginner.

I'd recommend an understanding of the problem Hibernate (and other ORMs) exist to fix. So a decent appreciation of what a relational database is and what the object-relational impedance mismatch is. Understanding the big picture helps enormously in understanding why Hibernate behaves the way it does.

You can get working on Hibernate with a modicum of knowledge of JDBC. Hibernate's own documentation is brief but clear. Its been a while since I read any books on Hibernate so my knowledge there is probably out of date. Books recommendations are dotted about in this forum; I'd recommend searching here and see what other people say. I would say that my experience is you don;t need a book to get started, they are more useful for explaining the more advanced topics.

Paul Sturrock wrote:I'd recommend an understanding of the problem Hibernate (and other ORMs) exist to fix. So a decent appreciation of what a relational database is and what the object-relational impedance mismatch is. Understanding the big picture helps enormously in understanding why Hibernate behaves the way it does.

You can get working on Hibernate with a modicum of knowledge of JDBC. Hibernate's own documentation is brief but clear. Its been a while since I read any books on Hibernate so my knowledge there is probably out of date. Books recommendations are dotted about in this forum; I'd recommend searching here and see what other people say. I would say that my experience is you don;t need a book to get started, they are more useful for explaining the more advanced topics.

Thanks...replies are appreciated.