typesafe

The concept of a single generic typesafe DAO had been a topic since the appearance of generics in the Java language.

I owe additional credit to Christian for looking at my first attempt at writing a generic typesafe DAO and suggesting improvements.

Why would you want a typesafe interface for your data access code?

The Criteria queries are portable and typesafe and are designed to work regardless of the data store used.

In this article, I show you how to avoid repeating DAO code over and over again, while still retaining the benefits of a typesafe interface.

At this point, I have a generic DAO capable of typesafe CRUD operations.

The generic DAO pattern (also called Typesafe DAO) is critical to reducing code duplication in the data access tier.

First of all, a typesafe interface clearly indicates which domain objects have persistent storage available.

From Typesafe you have Akka that greatly simplifies the distributed processing model to give robust messaging based computing like Erlang.

You can therefore apply filtering at this level in a typesafe manner.

While the code in Listing 8 is a correct way of using the typesafe PersonDao interface, the implementation of the DAO is not complete.

See Resources to learn about other generic typesafe DAO class implementations.

Declare a typesafe reference to a class method

Work effectively with typesafe constants in Java 5. 0