Skip to content

Commit

Permalink
ArC: consider built-in session context during client proxy optimization
Browse files Browse the repository at this point in the history
- the problem occurs when quarkus-websockets-next and quarkus-undertow
extensions are used at the same time
- fixes quarkusio#46548
  • Loading branch information
mkouba committed Feb 28, 2025
1 parent bc14c86 commit 8e3211c
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -591,6 +591,7 @@ private Set<DotName> findSingleContextNormalScopes() {
Map<DotName, Integer> contextsForScope = new HashMap<>();
// built-in contexts
contextsForScope.put(BuiltinScope.REQUEST.getName(), 1);
contextsForScope.put(BuiltinScope.SESSION.getName(), 1);
// custom contexts
for (Map.Entry<ScopeInfo, List<Function<MethodCreator, ResultHandle>>> entry : beanDeployment
.getCustomContexts()
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -176,6 +176,10 @@ Contexts build() {
// If a custom request context is registered then add the built-in context as well
putContext(requestContext);
}
if (contexts.containsKey(SessionScoped.class)) {
// If a custom session context is registered then add the built-in context as well
putContext(sessionContext);
}
return new Contexts(requestContext, sessionContext, applicationContext, singletonContext, dependentContext,
contexts);
}
Expand Down

0 comments on commit 8e3211c

Please sign in to comment.