ArC: make it possible to activate the session context for a specific business method in a test

[mkouba]

Description

Currently, it's not possible to test a @SessionScoped component used in a WS Next app outside the real websocket communication. That is quite limiting.

Implementation ideas

We could provide an annotation similar to @jakarta.enterprise.context.control.ActivateRequestContext.

[quarkus-bot]

/cc @Ladicek (arc), @manovotn (arc)

[mkouba]

Hm, I think that we should move the logic from WebSocketSessionContext into ArC because it does not contain anything WS Next-specific. It's actually almost identical to io.quarkus.arc.impl.RequestContext. So maybe we could also extract the logic in an abstract superclass.

[manovotn]

Hm, I think that we should move the logic from WebSocketSessionContext into ArC because it does not contain anything WS Next-specific. It's actually almost identical to io.quarkus.arc.impl.RequestContext. So maybe we could also extract the logic in an abstract superclass.

Wouldn't that lead to a possible conflict with Undertow extension impl of @SessionScoped?

[mkouba]

Hm, I think that we should move the logic from WebSocketSessionContext into ArC because it does not contain anything WS Next-specific. It's actually almost identical to io.quarkus.arc.impl.RequestContext. So maybe we could also extract the logic in an abstract superclass.

Wouldn't that lead to a possible conflict with Undertow extension impl of @SessionScoped?

It should not. First of all, it's perfectly fine to have multiple contexts registered for a scope. However, only one can be active at a given time. The plan is to only register the activating binding/interceptor for tests. And obviously, the interceptor should do nothing if the context is already active.

[manovotn]

The plan is to only register the activating binding/interceptor for tests. And obviously, the interceptor should do nothing if the context is already active.

Got it; in that case, it should be perfectly fine 👍