The specification of JEE defines, that only the ApplicationScope and DependentScope have to be activated within an executed thread (managed or non-managed). Hence, by executing asynchronous processes by ExecutorService.submit(process), an error is thrown because RequestContext is inactive, if RequestScoped beans are injected, used or produced anywhere during invocation. Now it could be the case, that you have a CDI-producer […]
A typical JEE application consists of or is devided in different EARs or WARs to seperate concerns or to be encoupled during updates. Usually two EARs, even within the same VM, communicate via REST, JMS or (hopefully not :)) via remote EJB. Since CDI steped into our enterprise world, developers started loving it. Nearly everything can be extended, produced […]