Well, that's definitely a popular request.
If we wanna support transactions, REQUIRES_NEW is the only relevant
attribute to use in my opinion.
I guess from the discussion that we want to support transactions in SFSB
and Singleton, but not yet for SLSB and MDB. Right?
Jean-Louis
2011/12/1 Reza Rahman <reza_rahman_at_lycos.com>
> I think this is the right change to make. In case of roll-back, the
> instance should become unusable. In this case REQUIRES==REQUIRES_NEW
>
>
> On 11/30/2011 8:54 PM, Marina Vatkina wrote:
>
>> Experts,
>>
>> Looking at the long thread on this subject (XXX Transactional execution
>> of a PostConstuct or PreDestroy method of a singleton session bean), I'm
>> confused on the outcome of the discussion...
>>
>> Did we reach an agreement to allow transactional support for Pre/Post
>> lifecycle callback methods of a SFSB (i.e. SLSB and MDB are not changed in
>> this release)?
>>
>> If yes, did we agree that Required would mean RequiresNew in the
>> transactional attributes (i.e. their execution is never a part of the
>> client's transaction)?
>>
>> What would happen with a SFSB instance if transaction is rolled back
>> during execution of the lifecycle callback?
>>
>> thanks,
>> -marina
>>
>>
>>
>>
>>
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2012.0.1873 / Virus Database: 2102/4649 - Release Date: 11/30/11
>>
>>
>>
>