Summary
This tutorial is the final part in a three-part series chronicling the building of
a Java-based calendar and reminder system that uses the Derby database
as its data storage system. Part 1 covered the basic database and e-mail
entities. Part 2 built those entities into a simple application
that explored Derby's embedded, network, and Web-based modes. It also introduced
the concept of multiple users.
This tutorial took the overall system and tackled concurrency, discussing
transactions, locking, and isolation levels. It also described significant
improvements to the overall look and feel and usability of the application.
You now have a system that can be used by multiple individuals at the
same time, all editing a common event calendar. You can also choose
whether or not to see data that has not yet been committed to the database.
10 of 13 |
Previous |
Next
Comments
Back to top
Help: Update or add to My dW interests
What's this?
This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.
And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.
View your My developerWorks profile
Return from help
static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Open source, Information Management
ArticleID=94193
TutorialTitle=Build a Derby calendar, Part 3: Using transactions and locking
publish-date=09272005
author1-email=ibmquestions@nicholaschase.com
author1-email-cc=