Workaround for lazy loaded collections for RealmEntity
--- Quarkus3 branch sync no. 13 (11.4.2023) Resolved conflicts: keycloak/model/jpa/src/main/java/org/keycloak/models/jpa/JpaRealmProvider.java - Modified
This commit is contained in:
parent
9796e69d8d
commit
28975b950d
1 changed files with 6 additions and 0 deletions
|
@ -166,6 +166,12 @@ 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