|
The problem might actually lie in ORM. There javax.persistence.spi.PersistenceProvider looks like:
org.hibernate.jpa.HibernatePersistenceProvider
# The deprecated provider, logs warnings when used.
org.hibernate.ejb.HibernatePersistence
And in Persistence#PersistenceUtil#isLoaded we have:
public boolean isLoaded(Object entity, String attributeName) {
List<PersistenceProvider> providers = Persistence.getProviders();
for ( PersistenceProvider provider : providers ) {
final LoadState state = provider.getProviderUtil().isLoadedWithoutReference( entity, attributeName );
if ( state == LoadState.UNKNOWN ) continue;
return state == LoadState.LOADED;
}
for ( PersistenceProvider provider : providers ) {
final LoadState state = provider.getProviderUtil().isLoadedWithReference( entity, attributeName );
if ( state == LoadState.UNKNOWN ) continue;
return state == LoadState.LOADED;
}
return true;
}
It looks like, all PersitenceProviders are iterated here leading to the warning described. I am wondering whether org.hibernate.ejb.HibernatePersistence should really still be listed in the service file!? Need to look more into it. In the end this is probably a HHH issue.
|
