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@lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
