Feedback on the idea of PersistenceProviderResolver.getPersistenceProviders() caching the same org.hibernate.ejb.HibernatePersistence class instance for multiple application deployments to share ...
3:02 p.m.
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.
3:39 p.m.
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
4:02 p.m.
What triggers Hibernate Validator to call
PersistenceProviderResolver.getPersistenceProviders()? Does this happen
during the call to
PersistenceProvider.createContainerEntityManagerFactory() or later after
application deployment completes?
I'm looking at changing
PersistenceProviderResolver.getPersistenceProviders() to cache the
results on a per deployment basis but need to know when the first call
will be made, so I don't break deployment of persistence providers in
the deployed application.
4:22 a.m.
PersistenceProvider implementations are not app specific.
Hibernate Validator uses
Persistence.getPersistenceUtil()
This in turn is a static reference object that in its method calls
Persistence.getProviders() *each time* to resolve operations like
isLoaded(entity).
So to answer your question, I think it's after.
On Fri 2014-09-12 17:02, Scott Marlow wrote:
What triggers Hibernate Validator to call
PersistenceProviderResolver.getPersistenceProviders()? Does this happen
during the call to
PersistenceProvider.createContainerEntityManagerFactory() or later after
application deployment completes?
I'm looking at changing
PersistenceProviderResolver.getPersistenceProviders() to cache the
results on a per deployment basis but need to know when the first call
will be made, so I don't break deployment of persistence providers in
the deployed application.
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
4:28 a.m.
BTW there can be multiple persistence units deployed per application so
if you are trying to tie your cache to the lifecycle of
createContainerEntityManagerFactory, you might be making a mistake.
On Wed 2014-09-17 11:22, Emmanuel Bernard wrote:
PersistenceProvider implementations are not app specific.
Hibernate Validator uses
Persistence.getPersistenceUtil()
This in turn is a static reference object that in its method calls
Persistence.getProviders() *each time* to resolve operations like
isLoaded(entity).
So to answer your question, I think it's after.
On Fri 2014-09-12 17:02, Scott Marlow wrote:
> What triggers Hibernate Validator to call
> PersistenceProviderResolver.getPersistenceProviders()? Does this happen
> during the call to
> PersistenceProvider.createContainerEntityManagerFactory() or later after
> application deployment completes?
>
> I'm looking at changing
> PersistenceProviderResolver.getPersistenceProviders() to cache the
> results on a per deployment basis but need to know when the first call
> will be made, so I don't break deployment of persistence providers in
> the deployed application.
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
2:01 p.m.
On 09/17/2014 05:28 AM, Emmanuel Bernard wrote:
BTW there can be multiple persistence units deployed per application
so
if you are trying to tie your cache to the lifecycle of
createContainerEntityManagerFactory, you might be making a mistake.
When applications include a persistence provider(s), we associate the
provider with the application classloader (saved in
PersistenceProviderResolver level cache). This is not tied to the
persistence unit. The call to
PersistenceProvider.createContainerEntityManagerFactory() can happen
before the PersistenceProviderResolver cache is updated with the
deployed provider.
So, it is important to understand when Hibernate Validator first calls
Persistence.getProviders(), so that we know to set the cache earlier.
This looked hard to do a few years ago (chicken + egg problem with when
application classloaders are known in WildFly from what I remember).
On Wed 2014-09-17 11:22, Emmanuel Bernard wrote:
> PersistenceProvider implementations are not app specific.
>
> Hibernate Validator uses
>
> Persistence.getPersistenceUtil()
>
> This in turn is a static reference object that in its method calls
> Persistence.getProviders() *each time* to resolve operations like
> isLoaded(entity).
>
> So to answer your question, I think it's after.
>
> On Fri 2014-09-12 17:02, Scott Marlow wrote:
>> What triggers Hibernate Validator to call
>> PersistenceProviderResolver.getPersistenceProviders()? Does this happen
>> during the call to
>> PersistenceProvider.createContainerEntityManagerFactory() or later after
>> application deployment completes?
>>
>> I'm looking at changing
>> PersistenceProviderResolver.getPersistenceProviders() to cache the
>> results on a per deployment basis but need to know when the first call
>> will be made, so I don't break deployment of persistence providers in
>> the deployed application.
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
3722
days inactive
3735
days old
5 comments
2 participants
participants (2)
-
Emmanuel Bernard -
Scott Marlow