[hibernate-dev] Should the TransactionSynchronizationRegistry be cached by the JtaPlatform or perhaps at the SessionFactory level?
smarlow at redhat.com
Wed Nov 28 15:58:41 EST 2018
I started working on a WildFly change WFLY-11243  to cache the
TransactionSynchronizationRegistry inside of the WildFly JtaPlatform
instance. The purpose of caching the TransactionSynchronizationRegistry
is to avoid repeated JndiService.locate() calls, like during entity
manager creation time  and other uses as well.
My question is whether the idea of caching the
TransactionSynchronizationRegistry instance is already handled at the
session factory level? If not, would that make sense?
 is the WildFly pr to cache the TransactionSynchronizationRegistry
instance, to avoid repeatedly looking it up (since it rarely ever
changes). If there is a way to instead have the
TransactionSynchronizationRegistry cached at the SF level, that might be
More information about the hibernate-dev