Support @RequestScoped beans in command line mode

Description Having

@RequestScoped
public class MyJPAService {
}

And the main class for a command line application:

@QuarkusMain
public class MainApplication implements QuarkusApplication {
    @Inject
    MyJPAService service;

    public static void main(String[] args) {
        Quarkus.run(MainApplication.class, args);
    }
    @Override
    public int run(String... args) throws Exception {
        System.out.println("Instance:  " + service);
        return 0;
    }
}

When I run mvn quarkus:dev, I get the following exception:

2020-04-22 13:29:50,255 ERROR [io.qua.run.Application] (Quarkus Main Thread) Error running Quarkus application: javax.enterprise.context.ContextNotActiveException: interface javax.enterprise.context.RequestScoped

A workaround is to call Arc.container().requestContext().activate(); in the MainApplication#run method (and deactivate when it’s done).

Implementation ideas Change the core implementation that calls my Main method to initialize the Arc container if a @RequestScoped class is used.

[mkouba]

@mkouba you mean users should be required to put Arc.container().requestContext().activate(); in every cli or that you think the context should just always be activated ?

Nope. We should either activate it automatically or encourage users to use @ActivateRequestContext.

[mkouba]

If you activate request context for the whole main method, it means it will be active from app start to its shutdown. That kind of defeats the purpose of the scope…

I believe that the intention is to support @RequestScoped beans during “quarkus command execution”. And the request context is not necessarlly bound to an HTTP request. There are few exceptions in the spec and we have few more in Quarkus. In this case, the command execution is a “request”.

Yes, @ActivateRequestContext should work.