HibernateJpaVendorAdapter causes Hibernate 4.3 to produce deprecation warnings [SPR-11240]

[spring-projects-issues]

Keir Lawson opened SPR-11240 and commented

When running my application using Hibernate 4.3 to provide JPA 2.1 I get the following error owing to HibernateJpaVendorAdapter using deprecated Hibernate classes:

[10:50:44 WARN ]HHH015016: Encountered a deprecated javax.persistence.spi.PersistenceProvider [org.hibernate.ejb.HibernatePersistence]; use [org.hibernate.jpa.HibernatePersistenceProvider] instead. (org.hibernate.ejb.HibernatePersistence)

---

Affects: 4.0 GA

Issue Links:

• HibernateJpaVendorAdapter should use new interface when on Hibernate 4.3 [SPR-11358] #15983 HibernateJpaVendorAdapter should use new interface when on Hibernate 4.3 ("is duplicated by")

Referenced from: commits 479d073

0 votes, 5 watchers

[spring-projects-issues]

Juergen Hoeller commented

Does this have a negative effect beyond the warn log entry? That is, does your application run fine in all other respects?

We're going to address this in some form anyway. I'd just like to find out about potential effects.

Juerge

[spring-projects-issues]

Juergen Hoeller commented

I've adapted orm.hibernate4 and HibernateJpaVendorAdapter to avoid deprecation warnings on Hibernate 4.3 final now, to be available in the next 4.0.1 snapshot.

HibernateJpaVendorAdapter reflectively checks for the presence of "org.hibernate.jpa.HibernatePersistenceProvider" and uses it if available. Otherwise, it falls back to the old "org.hibernate.ejb" package.

Juergen

[spring-projects-issues]

Keir Lawson commented

There is no immediately apparent effect beyond the log entry.

[spring-projects-issues]

Juergen Hoeller commented

Thanks - that's good to know.

Aside from JPA 2.1 support, we upgraded our orm.hibernate4 package (for native Hibernate API usage) to deal with Hibernate 4.3's refactored SPI packages. However, for Hibernate 4.3 as a JPA provider, we just did integration tests, and apparently didn't notice that log entry - or it wasn't there back when we tested (Hibernate 4.3 RC1).

Anyway, as of Spring 4.0.1, that log irritation is gone.

Juergen

[spring-projects-issues]

William Gorder commented

duplicate of https://jira.springsource.org/browse/SPR-10415 ?

Edit - never mind they are different. I was not reading closely.

[spring-projects-issues]

Ludovic Praud commented

Can this be done also on Spring 3.2.x ?

[spring-projects-issues]

Juergen Hoeller commented

Note that Spring Framework 3.2.x doesn't even support JPA 2.1, so we have no plans to support Hibernate 4.3 - as a JPA 2.1 provider - either. The combination might work to some degree, but well, the deprecation warning is fundamentally right then since Spring 3.2's JPA support isn't up to the expected level (by design).

Have you tried an upgrade to Spring Framework 4.0? Any issues preventing you from upgrading? With the upcoming 4.0.1 (scheduled for this Thursday), all reported issues against 4.0 GA will have been addressed. You could try a 4.0.1 snapshot in the meantime (see http://projects.spring.io/spring-framework/ for repo details).

Juergen