Hi, I would say no to #2. Thread != RequestScoped. If you want to start a request scope with the thread, DeltaSpike has a CDIControl module that can do this for you.
John On Mon, Oct 6, 2014 at 11:08 AM, Lars-Fredrik Smedberg <itsme...@gmail.com> wrote: > When executing an EJB @Asynchronous method I know that valid CDI scopes are > request and application. > > 1. Since @ApplicationScoped beans are available I assume that its better to > inject those in the actual code being executed rather than passing them as > arguments to the @Asynchronous method, correct? > 2. Since the @Asynchronous method starts a new thread any @RequestScoped > beans passed in will be recreated right when the first business method on > them are called, correct? > 3. The above leaves me (if correct) with choosing between passing a normal > POJO (created with new) or an injected @Dependent scoped CDI Managed Bean > to an @Asynchronous EJB method, the choice depends on wether the object > passed needs to inject anything, correct? > > -- > Med vänlig hälsning / Best regards > > Lars-Fredrik Smedberg > > STATEMENT OF CONFIDENTIALITY: > The information contained in this electronic message and any > attachments to this message are intended for the exclusive use of the > address(es) and may contain confidential or privileged information. If > you are not the intended recipient, please notify Lars-Fredrik Smedberg > immediately at itsme...@gmail.com, and destroy all copies of this > message and any attachments. >
