Yoeri smets I was asking Adrian Meredith specifically, as he was talking about Hibernate 4.3.

But in general, I cannot help y'all with GlassFish. This is a Jira for development of Hibernate. I do no development on GlassFish and have never looked at nor touched their code. As for EE7, that is largely in flux between implementors of the various specs at the moment as it was just very recently finalized.

For JPA specifically, while the user API is always backwards compatible, each rev does introduce minor changes in the "container contracts" (aka, the SPI between the EE container and the JPA provider). So the level of difficulty there is going to increase if you try to bundle a JPA provider that implements an older version of the spec into containers implementing newer versions. Not impossible, just something to be aware of. Better bet would be to integrate Hibernate with GlassFish (if they have not already) and use that GF provided Hibernate.

As an example, the original issue report mentions a problem calling EntityManagerFactory.createEntityManager(javax.persistence.SynchronizationType, java.util.Map). Well thats a new method added in JPA 2.1. That won't work with Hibernate 4.2 or earlier as 4.2 is JPA 2.0 compliant.

As for the problem with InjectedDataSourceConnectionProvider, who tries to set that up? This is a problem, because that class is no longer in the codebase. There was always questionable need for it. More than likely GlassFish was using that to attempt to pass in (inject) the DataSource to use rather than having Hibernate look it up via JNDI. But there has always been other (better) ways to do that. At any rate, references to InjectedDataSourceConnectionProvider will not work in Hibernate 4.3 onwards.