|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2529 | minor | always | 03-14-08 13:14 | 04-08-08 14:33 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.1.5 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.6 | ||
|
|
|||||
| Summary: | 0002529: EJB XA bean issue | ||||
| Description: |
(rep by Daniel D'Alessandro) I've noticed a fairly major change in the transactional behaviour in the snapshot from 2008-03-04 basically if I have a session bean set up in the following manner public interface IFoo { public method1(); public method2(); } @Stateless @Local ({IFoo.class}) @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) public class FooImpl implements IFoo { public method1() { //do stuff } public method2() { method1() //do stuff } } now under the older resin (and other appservers I've used) the call from method2 to method1 would not result in a new transaction, instead method1 would participate in the transaction started by method2. To get the requires new you would have to call another instance of Foo. In the snapshot method1 called in this manner will start a new transaction if it is on the local interface. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||