rsh-dal web site

The RSH DAL package provides a standard data access toolkit. By programming to the rsh-dal API, a program or application is then insulated from data access implementation details. This means you could use straight JDBC and then move to Hibernate3 without having to change the code in your DAOs. Additionally, the rsh-dal tries to enforce some general principles on its DAS implementations that make building and testing applications much easier.

The key advantages to using rsh-dal are as follows:

• Implementation Agnostic
  Your DAOs no longer care how data is retrieved, since that is performed by the rsh-dal and its support libraries. So you can focus on business logic and migrate to new technologies with little or no changes to your actual code. Migration becomes more a matter of configuration and retooling support classes your DAOs have no direct knowledge of.
• Works With or Without J2EE, With or Without a DataSource
  The rsh-dal and its support libraries take care of obtaining connections and interacting wtih JTA, regardless of the environment you are in. This makes building and testing applications much easier, since you do not have to wait and fully-deploy your application only to find out you goofed your SQL statement.
• Standard Facilities for JDBC Interaction
  Even if you choose not to leverage the data access strategies of rsh-dal (and you really should), you can use the standard JDBC connection management, Handler interfaces, SQL mapping management, and more when you build your own application. This dramatically reduces the effort and testing involved to build a new application that is JDBC based.

Through rsh-dal and its foundational libraries, you get these abilities and many more for free. The goal of rsh-dal is to stop re-implementing some of the glue that always is required in a new application--glue that is required whether you use JDBC or Hibernate3 or some other toolkit.