www.arjuna.com news company products standards research library forums contact
Trail map 1. Installation Content 2. The Sample Application 3. Deploying and Testing the Sample Application 4. Making the Sample Application Persistent 5. Recovery From Failure 6. Where Next? Navigation Home Previous Next Additional Trails Distributed Transaction Processing The X/Open DTP Model The OMG OTS Model Transactions in J2EE Configuring ATS Configuring the Recovery Manager ORB Portability Transactional Object For Java
| print this page
| email this page
Making the Banking Application Persistent The way the banking application is built and deployed in the previous trail does not it make it persistent, in such way that any created account can be retrieved later after stopping the bank server or if the application crashes; moreover, it does not allow concurrent access to accounts without leading to inconsistent values. Two ways will be presented in this trail on the way to build the banking application as a persistent and sharable application: Using the Arjuna Transactional Object For Java (TXOJ) mechanisms Overview of the Transactional Object For Java Deploying the Banking application with TXOJ mechanisms Using the JDBC API by considering the banking application as a relational database. Developing applications with JDBC and ArjunaTA The banking application as a relational database accessed with JDBC
Copyright 2002-2005 Arjuna Technologies All Rights Reserved. info@arjuna.com +44 191 243 0676