Arc - tweak ContextNotActiveException for session scoped beans to mention optional enablement

[manovotn]

Fixes #45191

Using the reproducer from original issue, the exception now looks like this:

jakarta.enterprise.context.ContextNotActiveException: SessionScoped context was not active when trying to obtain a bean instance for a client proxy of PRODUCER_METHOD bean [class=io.quarkus.ts.spring.data.primitivetypes.configuration.AppConfiguration, id=9767shscEaYLEayHF-_VBq-X1Aw]
- @SessionScoped is not supported by default. However, a Quarkus extension implementing session context can be used to enable this functionality (such as Undertow extension).

[Ladicek]

I think we should do this also for the conversation context, but that's more complex and can be subject of a different PR. This PR LGTM.

[manovotn]

I think we should do this also for the conversation context, but that's more complex and can be subject of a different PR.

I don't think ArC should solve that since we don't support it in any shape or form (and CDI Lite doesn't support it either).
That being said, if you are both in favor, I can send a PR with that as well. It should be simple enough.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit bb7c3b1.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[mkouba]

I think we should do this also for the conversation context, but that's more complex and can be subject of a different PR.

I don't think ArC should solve that since we don't support it in any shape or form (and CDI Lite doesn't support it either). That being said, if you are both in favor, I can send a PR with that as well. It should be simple enough.

Right, and since we don't support this scope annotation in any form we should probably fail the build. Currently, we silently ignore this scope declared on a class and fall back to @Dependent for a producer.

[Ladicek]

Right, and since we don't support this scope annotation in any form we should probably fail the build. Currently, we silently ignore this scope declared on a class and fall back to @Dependent for a producer.

Technically someone could provide the conversation context implementation and expect that to work, but I agree with a build failure, at least for now.

[manovotn]

Alright, I've created #45413 to track the conversation scope change.
I can most likely look into it some time later this week.