From: Marina Vatkina <Marina.Vatkina_at_Sun.COM>
Date: Mon, 29 Jun 2009 11:10:09 -0700

This is what the spec says:

4.5.3 Transactions
Client transaction context does not propagate with an asynchronous method
invocation. From the Bean Developer’s view, there is never a transaction context
flowing in from the client. This means, for example,
that the semantics of the REQUIRED transaction attribute on an asynchronous
method are exactly the same as REQUIRES_NEW.

HTH,
-marina

Felipe Gaúcho wrote:
> no. just a chain of EJBs...
>
> On Mon, Jun 29, 2009 at 7:57 PM, Marina Vatkina<Marina.Vatkina_at_sun.com> wrote:
>
>>Are you managing threads in addition to using EJB options?
>>
>>thanks,
>>-marina
>>
>>Felipe Gaúcho wrote:
>>
>>>If I use @Asynchronous in the new Java EE api,
>>>
>>>if I have a transactional request, asynchronous, and the original
>>>request thread depends on sub-threads, how the original transaction
>>>behave ?
>>>
>>>if any children fail it fail ? it will wait for all asynchronous
>>>sub-threads ? for how long ?
>>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>
>
>
>