You can absolutely do what you mention and use @RequestScoped beans in an @Stateless session bean and an @MessageDriven bean. This is a core part of the CDI spec and TCK and guaranteed portable. Note on MDBs Do be aware that there is a test for a @Stateless bean that uses a @RequestScoped bean, but … Read more
If only 1 timer may ever be active at the same time, there are a couple of solutions. First of all the @Timer should probably be present on an @Singleton. In a Singleton methods are by default write-locked, so the container will automatically be locked-out when trying to invoke the timer method while there’s still … Read more
An important motivation for having EJB beans in a separate JAR is for the age old separation of business logic and view logic. Since EJBs are supposed to concentrate solely on business logic, it makes sense to put them into a separate module. This is exactly what the traditional Java Enterprise Archive facilitates. The EJB … Read more
Stateless Session Beans (SLSB) are not tied to one client and there is no guarantee for one client to get the same instance with each method invocation (some containers may create and destroy beans with each method invocation session, this is an implementation-specific decision, but instances are typically pooled – and I don’t mention clustered … Read more