Remove workaround for Lazy initialization of Realm's collections
Closes #19069
This commit is contained in:
parent
a020d3f6df
commit
d962dec954
1 changed files with 0 additions and 6 deletions
|
@ -166,12 +166,6 @@ public class JpaRealmProvider implements RealmProvider, ClientProvider, ClientSc
|
||||||
if (realm == null) {
|
if (realm == null) {
|
||||||
return false;
|
return false;
|
||||||
}
|
}
|
||||||
|
|
||||||
// Workaround tracked by issue https://github.com/keycloak/keycloak/pull/19069
|
|
||||||
// As of Hibernate 6.2.0.CR3, after the em.refresh(entity) the lazily loaded collections in realm don't load anymore, instead there is a
|
|
||||||
// LazyInitializationException. As a workaround, comment out the refresh call.
|
|
||||||
// em.refresh(realm);
|
|
||||||
|
|
||||||
final RealmAdapter adapter = new RealmAdapter(session, em, realm);
|
final RealmAdapter adapter = new RealmAdapter(session, em, realm);
|
||||||
session.users().preRemove(adapter);
|
session.users().preRemove(adapter);
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue