Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Wrong warning about deprecated persistence provider

Description

I upgraded my current WildFly snapshot from Hibernate 4.3.0.Beta4 to Beta5 (and used the snapshot for Hibernate core due to HHH-8613).

However, I'm getting the warning below even if I declare a persistence provider in META-INF/persistence.xml:

<persistence-unit name="shopPU"> <provider>org.hibernate.jpa.HibernatePersistenceProvider</provider> ...

The warning

HHH015016: Encountered a deprecated javax.persistence.spi.PersistenceProvider [org.hibernate.ejb.HibernatePersistence]; use [org.hibernate.jpa.HibernatePersistenceProvider] instead.

Attachments

2
  • 21 Nov 2013, 09:41 AM
  • 18 Nov 2013, 01:49 PM

Activity

Marcel StörMay 8, 2014 at 8:55 AM

@reijava since this issue is closed I suggest you add your comments to HHH-9141.

Reinaldo de CarvalhoApril 21, 2014 at 9:11 PM

I am using 4.3.5.Final version from Maven Repository and still got the same error.

My META-INF/persistence.xml:

<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd" version="2.0"> <persistence-unit name="pu1"> <provider>org.hibernate.jpa.HibernatePersistenceProvider</provider> <properties> <property name="javax.persistence.jdbc.driver" value="org.postgresql.Driver" /> <property name="javax.persistence.jdbc.url" value="jdbc:postgresql://localhost:5432/jpa" /> <property name="javax.persistence.jdbc.user" value="postgres" /> <property name="javax.persistence.jdbc.password" value="********" /> <property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQL9Dialect" /> <property name="hibernate.show_sql" value="true" /> <property name="hibernate.format_sql" value="true" /> <property name="hibernate.hbm2ddl.auto" value="update" /> </properties> </persistence-unit> </persistence>

Brett MeyerMarch 7, 2014 at 10:08 PM

Bulk closing tickets resolved in released versions

Steve EbersoleDecember 31, 2013 at 1:13 AM

The ProviderUtil#isLoadedWithoutReference/ProviderUtil#isLoadedWithReference cases are interesting. I created a new issue doing some work there: HHH-8735

The underlying problem, as Scott pointed out, is the non-contextual nature of Persistence#isLoaded forcing it to ask isLoadedWithoutReference/isLoadedWithReference of every known JPA provider. The solution is likely to simply log this deprecation warning just on:

  • createEntityManagerFactory

  • createContainerEntityManagerFactory

  • generateSchema

(as well as on getEntityManagerFactoryBuilderOrNull)

Let's discuss (if need be) on HHH-8735

Juergen ZimmermannNovember 25, 2013 at 8:28 AM

here is an example for a JAX-RS class with Bean Validation, but without a JPA EntityManager:

@Path("/customers") @Produces({ ... }) @Consumes @RequestScoped @Transactional public class CustomerResource { @Context private UriInfo uriInfo; @Inject private CustomerService cs; @POST @Consumes({ ... }) @Produces public Response createCustomer(@Valid AbstractCustomer customer) { ...} }
Fixed

Details

Assignee

Reporter

Time tracking

0.65h logged

Components

Fix versions

Affects versions

Priority

Created October 17, 2013 at 2:08 PM
Updated May 8, 2014 at 8:55 AM
Resolved October 17, 2013 at 4:09 PM

Flag notifications