Skip to main content


developerWorks  >  Open source | Java technology | Information Management  >

Improve persistence with Apache Derby and iBATIS, Part 3: Transactions, caching, and dynamic SQL

developerWorks

Level: Intermediate

Daniel Wintschel (daniel@humandoing.net), Freelance writer

07 Mar 2006

Register now or sign in using your IBM ID and password.

This tutorial series has been demonstrating how you can improve persistence in your database-driven Java applications by combining Apache Derby's power as a small-footprint embeddable database with the iBATIS object-relational (OR) mapping framework. In Part 3, the final in the series, learn how iBATIS handles three advanced features of database-driven applications: transactions, caching, and dynamic SQL. Plus, find out how the Data Access Objects (DAO) framework can operate on its own without the Data Mapper framework.

In this tutorial

  • Transactions using Derby and iBATIS

  • Caching in iBATIS

  • Dynamic SQL in iBATIS

  • Standalone DAO example

Prerequisites

This tutorial assumes you're comfortable working with basic SQL statements, that you understand basic XML semantics, and that you can read Java code. You need to know how to run Apache Ant to follow the tutorial's examples and create the database.


System requirements

To run the example code in this tutorial, you need to:

  • Download and install several applications.
  • Define environmental variables.
  • Extract the .zip file.
  • Modify a .properties file.


Duration

Under 2 hours


Formats

html, pdf


Share this....

digg Digg this story del.icio.us del.icio.us Slashdot Slashdot it!


Back to top


Document options

Document options requiring JavaScript are not displayed


More in this series:
Improve persistence with Apache Derby and iBATIS