Name | Date | Size | |
---|---|---|---|
.. | 2012-03-06 15:30:16 | 9 | |
build.properties | 2012-03-06 15:30:16 | 2.5 KiB | |
build.xml | 2012-03-06 15:30:16 | 6.8 KiB | |
client | 2012-03-06 15:30:16 | 3 | |
client-jbi.xml | 2012-03-06 15:30:16 | 2.4 KiB | |
client-sun-web.xml | 2012-03-06 15:30:16 | 2.2 KiB | |
client-web.xml | 2012-03-06 15:30:16 | 3.1 KiB | |
dummy-client-su | 2012-03-06 15:30:16 | 4 | |
endpoint | 2012-03-06 15:30:16 | 3 | |
README | 2012-03-06 15:30:16 | 543 | |
sun-web.xml | 2012-03-06 15:30:16 | 2.2 KiB | |
web.xml | 2012-03-06 15:30:16 | 2.9 KiB | |
webclient | 2012-03-06 15:30:16 | 5 |
README
This tests the rollback logic of transaction. An EJB webservice is invoked by a servlet. This webservice method uses REQUIRED TX_Attribute.
Here is the flow-
1. Standalone client invokes a servlet
2. Servlet creates table CUSTOMER_rb1
3. Servlet starts a UserTransaction
4. Servlet adds a row in the CUSTOMER_rb1 table
5. Servlet calls the EJB webservice
6. EJB webservice adds a row in the CUSTOMER_rb1 table
7. Servlet rollback the transaction
8. It is checked that the data is not updated in the table.
9. Table CUSTOMER_rb1 is dropped