Never mind, we will look at caching the PersistenceProvider class
instance at the application deployment level (in WildFly).
On 09/12/2014 04:02 PM, Scott Marlow wrote:
Hello,
How would Hibernate ORM react to its persistence provider class instance
being used with multiple application deployments? Is there any "per
application" state in the ORM persistence provider class instance?
A few different implementations of
javax.persistence.spi.PersistenceProviderResolver.getPersistenceProviders()
are not caching the returned PersistenceProvider class instances. [1]
raised the issue with the WildFly
PersistenceProviderResolver.getPersistenceProviders() not caching the
provider class instances for reuse.
Same question for OGM, is there any "per application state" in the OGM
persistence provider class?
Scott
[1]
http://lists.jboss.org/pipermail/wildfly-dev/2014-September/002984.html
is the thread which raised this as a performance issue.
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev