Raible's Wiki: CreateDAO

At line 2 removed 394 lines.

!!About this tutorial

This tutorial will show you how to create a new table in the database, and how the create Java code to access this table.

We will create an object and then some more classes to persist (save/retrieve/delete) that object from the database. In Java speak, we call the object a Plain Old Java Object (a.k.a. a [POJO|http://forum.java.sun.com/thread.jsp?forum=92&thread=425300&tstart=0&trange=15]). This object basically represents a database table. The ''other classes'' will be:

* A Data Access Object (a.k.a. a [DAO|http://java.sun.com/blueprints/patterns/DAO.html]), an [Interface|http://java.sun.com/docs/books/tutorial/java/concepts/interface.html] and a Hibernate Implementation

* A [JUnit|http://www.junit.org] class to test our DAO is working

%%note __NOTE:__ If you're using MySQL and you want to use transactions (which you probably will) you have to use InnoDB tables. To do this, add the following to your mysql configuration file ({{/etc/my.cnf}} or {{c:\Windows\my.ini}}). The 2nd setting (for a UTF-8 character set) is needed for 4.1.7+.

{{{

[mysqld]

default-table-type=innodb

default-character-set=utf8

}}}

If you're using PostgreSQL and you get confusing errors about batch processing, try turning it off by adding {{<prop key="hibernate.jdbc.batch_size">0</prop>}} to your {{src/dao/**/hibernate/applicationContext-hibernate.xml}} file.

AppFuse uses [Hibernate|http://www.hibernate.org] for its default persistence layer. Hibernate is an Object/Relational (O/R) Framework that allows you to relate your Java Objects to database tables. It allows you to very easily perform CRUD (Create, Retrieve, Update, Delete) on your objects.

;:''You can also use [iBATIS|http://ibatis.com] as a persistence framework option. To install iBATIS in AppFuse, view the README.txt in {{extras/ibatis}}. If you're using iBATIS over Hibernate, I expect you have your reasons and are familiar with the framework. I also expect that you can figure out how to adapt this tutorial to work with iBATIS. ;-)''

!Font Conventions (work in progress)

;:Literal strings intended to be executed at the command prompt look like this: __ant test-all__.

;:References to files, directories and packages which exist in your source tree: <font size="2">{{build.xml}}</font>.

;:%%(color: blue)''And suggestions for how to do stuff in the "Real World" are in blue italics.''%%

Let's get started on creating a new Object, DAO and Test in AppFuse's project structure.

!Table of Contents

* [1] Create a new Object and add [XDoclet|http://xdoclet.sf.net] tags

* [2] Create a new database table from the object using Ant

* [3] Create a new DaoTest to run JUnit tests on the DAO

* [4] Create a new DAO to perform CRUD on the object

* [5] Configure Spring for the Person object and PersonDao

* [6] Run the DaoTest

!!Create a new Object and add XDoclet tags [#1]

The first thing we need to do is create an object to persist. Let's create a simple "Person" object (in the {{src/dao/**/model}} directory) that has an id, a firstName and a lastName (as properties).

%%note __NOTE:__ Copying the Java code in these tutorials [doesn't work in Firefox|http://raibledesigns.com/page/rd?anchor=java2html_plugin_for_jspwiki_causes]. A workaround is to CTRL+Click (Command+Click on OS X) the code block and then copy it.%%

[{Java2HtmlPlugin

package org.appfuse.model;

public class Person extends BaseObject {

private Long id;

private String firstName;

private String lastName;

Generate your getters and setters using your favorite IDE:

In Eclipse:

Right-click -> Source -> Generate Getters and Setters

}

}]

This class should extend [BaseObject|http://raibledesigns.com/downloads/appfuse/api/org/appfuse/model/BaseObject.java.html], which has 3 abstract methods: (equals(), hashCode() and toString()) that you will need to implement in the Person class. The first two are required by Hibernate. The easiest way to do this is using [Commonclipse|http://commonclipse.sf.net]. More information on using this tool can be found on [Lee Grey's site|http://www.leegrey.com/hmm/2004/09/29/1096491256000.html]. Another Eclipse Plugin you can use is [Commons4E|http://commons4e.berlios.de/]. I haven't used it, so I can't comment on its functionality.

;:''If you're using [IntelliJ IDEA|http://www.jetbrains.com/idea], you can generate equals() and hashCode(), but not toString(). There is a [ToStringPlugin|http://www.intellij.org/twiki/bin/view/Main/ToStringPlugin] that works reasonably well.''

Now that we have this POJO created, we need to add XDoclet tags to generate the Hibernate mapping file. This mapping file is used by Hibernate to map objects → tables and properties (variables) → columns.

First of all, we add a [@hibernate.class|http://xdoclet.sourceforge.net/tags/hibernate-tags.html#@hibernate.class%20(0..1)] tag that tells Hibernate what table this object relates to:

[{Java2HtmlPlugin

/**

* @hibernate.class table="person"

public class Person extends BaseObject {

}]

We also have to add a primary key mapping or XDoclet will puke when generating the mapping file. Note that all @hibernate.* tags should be placed in the __getters'__ Javadocs of your POJOs.

[{Java2HtmlPlugin

/**

* @return Returns the id.

* @hibernate.id column="id"

* generator-class="increment" unsaved-value="null"

public Long getId() {

return this.id;

}

}]

;:%%(color: blue)''I'm using {{generator-class="increment"}} instead of {{generate-class="native"}} because I [found some issues|AppFuseOnDB2] when using "native" on other databases. If you only plan on using MySQL, I __recommend you use the "native" value__. This tutorial uses increment.''%%

!!Create a new database table from the object using Ant [#2]

At this point, you can create the person table by running __ant setup-db__. This task creates the {{Person.hbm.xml}} file and creates a database table called "person". From the ant console, you can see the table schema the Hibernate creates for you:

{{{

[schemaexport] create table person (

[schemaexport] id bigint not null,

[schemaexport] primary key (id)

[schemaexport] );

}}}

If you want to look at the {{Person.hbm.xml}} file that Hibernate generates for you, look in the {{build/dao/gen/**/model}} directory. Here's the contents of {{Person.hbm.xml}} (so far):

[{Java2HtmlPlugin

<?xml version="1.0"?>

<!DOCTYPE hibernate-mapping PUBLIC

"-//Hibernate/Hibernate Mapping DTD 2.0//EN"

"http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">

<hibernate-mapping>

<class

name="org.appfuse.model.Person"

table="person"

dynamic-update="false"

dynamic-insert="false"

<id

name="id"

column="id"

type="java.lang.Long"

unsaved-value="null"

</generator>

</id>

<!--

To add non XDoclet property mappings, create a file named

hibernate-properties-Person.xml

containing the additional properties and place it in your merge dir.

-->

</class>

</hibernate-mapping>

}]

Now we'll add additional [@hibernate.property|http://xdoclet.sourceforge.net/tags/hibernate-tags.html#@hibernate.property%20(0..1)] tags for our other columns (first_name, last_name):

[{Java2HtmlPlugin

/**

* @hibernate.property column="first_name" length="50"

public String getFirstName() {

return this.firstName;

}

/**

* @hibernate.property column="last_name" length="50"

public String getLastName() {

return this.lastName;

}

}]

In this example, the only reason for adding the ''column'' attribute is because the column name is different from our property name. If they're the same, you don't need to specify the ''column'' attribute. See the [@hibernate.property|http://xdoclet.sourceforge.net/tags/hibernate-tags.html#@hibernate.property%20(0..1)] reference for other attributes you can specify for this tag.

Run __ant setup-db__ again to get the additional columns added to your table.

{{{[schemaexport] create table person (

[schemaexport] id bigint not null,

[schemaexport] first_name varchar(50),

[schemaexport] last_name varchar(50),

[schemaexport] primary key (id)

[schemaexport] );}}}

If you want to change the size of your columns, modify the ''length'' attribute in your @hibernate.property tag. If you want to make it a required field (NOT NULL), add not-null="true".

!!Create a new DaoTest to run JUnit tests on your DAO [#3]

%%note <a name="appgen"></a>__NOTE:__ AppFuse versions 1.6.1+ contain include an [AppGen] tool that can be used to generate all the classes for the rest of these tutorials. However, it's best that you go through these tutorials before using this tool - then you'll know what code it's generating.%%

Now we'll create a DaoTest to test that our DAO works. "Wait a minute," you say, "we haven't created a DAO!" You are correct. However, I've found that [Test-Driven Development|http://www.artima.com/intv/testdriven.html] breeds higher quality software. For years, I thought __write your test before your class__ was hogwash. It just seemed stupid. Then I tried it and I found that it works great. The only reason I do all this test-driven stuff now is because I've found it rapidly speeds up the process of software development.

To start, create a {{PersonDaoTest.java}} class in the {{test/dao/**/dao}} directory. This class should extend [BaseDaoTestCase|http://raibledesigns.com/downloads/appfuse/api/org/appfuse/dao/BaseDaoTestCase.java.html], a subclass of JUnit's [TestCase|http://junit.sourceforge.net/javadoc/junit/framework/TestCase.html] which already exists in this package. This parent class is used to load [Spring's|http://www.springframework.org] ApplicationContext (since Spring binds the layers together), and for (optionally) loading a .properties file (ResourceBundle) that has the same name as your {{*Test.class}}. In this example, if you put a {{PersonDaoTest.properties}} file in the same directory as {{PersonDaoTest.java}}, this file's properties will be available via an "rb" variable.

;:%%(color: blue)''I usually copy (open → save as) an existing test (i.e. UserDaoTest.java) and find/replace [[Uu]ser with [[Pp]erson, or whatever the name of my object is.''%%

[{Java2HtmlPlugin

package org.appfuse.dao;

import org.appfuse.model.Person;

import org.springframework.dao.DataAccessException;

public class PersonDaoTest extends BaseDaoTestCase {

private Person person = null;

private PersonDao dao = null;

protected void setUp() throws Exception {

super.setUp();

dao = (PersonDao) ctx.getBean("personDao");

}

protected void tearDown() throws Exception {

super.tearDown();

dao = null;

}

}]

The code you see above is what we need for a basic JUnit test that initializes and destroys our PersonDao. The "ctx" object is a reference to Spring's ApplicationContext, which is initialized in a static block of the [BaseDaoTestCase's|http://raibledesigns.com/downloads/appfuse/api/org/appfuse/dao/BaseDaoTestCase.java.html] class.

Now we need to actually test that the CRUD (create, retrieve, update, delete) methods work in our DAO. To do this we created methods that begin with "test" (all lower case). As long as these methods are public, have a void return type and take no arguments, they will be called by our <junit> task in our Ant build.xml file. Here's some simple tests for testing CRUD. An important thing to remember is that each method (also known as a test), should be autonomous. Add the following methods to your {{PersonDaoTest.java}} file:

[{Java2HtmlPlugin

public void testGetPerson() throws Exception {

person = new Person();

person.setFirstName("Matt");

person.setLastName("Raible");

dao.savePerson(person);

assertNotNull(person.getId());

person = dao.getPerson(person.getId());

assertEquals(person.getFirstName(), "Matt");

}

public void testSavePerson() throws Exception {

person = dao.getPerson(new Long(1));

person.setFirstName("Matt");

person.setLastName("Last Name Updated");

dao.savePerson(person);

if (log.isDebugEnabled()) {

log.debug("updated Person: " + person);

}

assertEquals(person.getLastName(), "Last Name Updated");

}

public void testAddAndRemovePerson() throws Exception {

person = new Person();

person.setFirstName("Bill");

person.setLastName("Joy");

dao.savePerson(person);

assertEquals(person.getFirstName(), "Bill");

assertNotNull(person.getId());

if (log.isDebugEnabled()) {

log.debug("removing person...");

}

dao.removePerson(person.getId());

try {

person = dao.getPerson(person.getId());

fail("Person found in database");

} catch (DataAccessException dae) {

log.debug("Expected exception: " + dae.getMessage());

assertNotNull(dae);

}

}]

;:%%(color: blue)''In the testGetPerson method, we're creating a person and then calling a get. I usually enter a record in the database that I can always rely on. Since [DBUnit|http://www.dbunit.org] is used to populate the database with test data before our tests are run, you can simply add the new table/record to the metadata/sql/sample-data.xml file:''%%

{{{

<column>first_name</column>

<row>

<value>Raible</value>

</row>

</table>

}}}

</div>

;:%%(color: blue)''This way, you can eliminate the "create new" functionality in the testGetPerson method. If you'd rather add this record directly into the database (via SQL or a GUI), you can rebuild your {{sample-data.xml}} file using __ant db-export__ and then __cp {{db-export.xml metadata/sql/sample-data.xml}}__.''%%

In the above example, you can see that we're calling person.set*(value) to populate our object before saving it. This is easy in this example, but it could get quite cumbersome if we're persisting an object with 10 required fields (not-null="true"). This is why I created the ResourceBundle in the BaseDaoTestCase. Simply create a {{PersonDaoTest.properties}} file in the same directory as {{PersonDaoTest.java}} and define your property values inside it:

;:%%(color: blue)''I tend to just hard-code test values into Java code - but the .properties file is an option that works great for large objects.''%%

{{{

firstName=Matt

lastName=Raible

}}}

Then, rather than calling person.set* to populate your objects, you can use the BaseDaoTestCase.populate(java.lang.Object) method:

[{Java2HtmlPlugin

person = new Person();

person = (Person) populate(person);

}]

At this point, the PersonDaoTest class won't compile yet because there is no PersonDao.class in our classpath, we need to create it. PersonDAO.java is an interface, and PersonDAOHibernate.java is the Hibernate implementation of that interface. Let's go ahead and create those.

!!Create a new DAO to perform CRUD on the object [#4]

First off, create a PersonDao.java interface in the {{src/dao/**/dao}} directory and specify the basic CRUD methods for any implementation classes. ''I've eliminated the JavaDocs in the class below for display purposes.''

[{Java2HtmlPlugin

package org.appfuse.dao;

import org.appfuse.model.Person;

public interface PersonDao extends Dao {

public Person getPerson(Long personId);

public void savePerson(Person person);

public void removePerson(Long personId);

}

}]

Notice in the class above there are no exceptions on the method signatures. This is due to the power of [Spring|http://www.springframework.org] and how it wraps Exceptions with RuntimeExceptions. At this point, you should be able to compile all the source in {{src/dao}} and {{test/dao}} using __ant compile-dao__. However, if you try to run __ant test-dao -Dtestcase=PersonDao__, you will get an error: <span style="color: red">No bean named 'personDao' is defined</span>. This is an error message from Spring - indicating that we need to specify a bean named ''personDAO'' in {{applicationContext-hibernate.xml}}. Before we do that, we need to create the PersonDao implementation class.

;:''The ant task for running dao tests is called __test-dao__. If you pass in a testcase parameter (using __-Dtestcase=name__), it will look for {{**/*${testcase}*}} - allowing us to pass in Person, PersonDao, or PersonDaoTest - all of which will execute the PersonDaoTest class.''

Let's start by creating a PersonDaoHibernate class that implements the methods in PersonDao and uses Hibernate to get/save/delete the Person object. To do this, create a new class in {{src/dao/**/dao/hibernate}} and name it {{PersonDAOHibernate.java}}. It should extend [BaseDaoHibernate|http://raibledesigns.com/downloads/appfuse/api/org/appfuse/dao/BaseDAOHibernate.java.html] and implement PersonDAO. ''Javadocs eliminated for brevity.''

[{Java2HtmlPlugin

package org.appfuse.dao.hibernate;

import org.appfuse.model.Person;

import org.appfuse.dao.PersonDao;

import org.springframework.orm.ObjectRetrievalFailureException;

public class PersonDaoHibernate extends BaseDaoHibernate implements PersonDao {

public Person getPerson(Long id) {

Person person = (Person) getHibernateTemplate().get(Person.class, id);

if (person == null) {

throw new ObjectRetrievalFailureException(Person.class, id);

}

return person;

}

public void savePerson(Person person) {

getHibernateTemplate().saveOrUpdate(person);

}

public void removePerson(Long id) {

// object must be loaded before it can be deleted

getHibernateTemplate().delete(getPerson(id));

}

}]

Now, if you try to run __ant test-dao -Dtestcase=PersonDao__, you will get the same error. We need to configure Spring so it knows that PersonDaoHibernate is the implementation of PersonDAO, and we also need to tell it about the Person object.

!!Configure Spring for the Person object and PersonDao [#5]

First, we need to tell Spring where the Hibernate mapping file is located. To do this, open {{src/dao/**/dao/hibernate/applicationContext-hibernate.xml}} and add {{"Person.hbm.xml"}} to the following code block.

[{Java2HtmlPlugin

<list>

<value>org/appfuse/model/Person.hbm.xml</value>

<value>org/appfuse/model/Role.hbm.xml</value>

<value>org/appfuse/model/User.hbm.xml</value>

<value>org/appfuse/model/UserCookie.hbm.xml</value>

</list>

</property>

}]

Now we need to add some XML to this file to bind PersonDaoHibernate to PersonDao. To do this, add the following at the bottom of the file:

[{Java2HtmlPlugin

</bean>

}]

;:''You could also use __autowire="byName"__ to the <bean> and get rid of the "sessionFactory" property''. %%(color: blue)''Personally, I like having the dependencies of my objects documented (in XML).''%%

!!Run the DaoTest [#6]

Save all your edited files and try running __ant test-dao -Dtestcase=PersonDao__ one more time.

__Yeah Baby, Yeah:__

%%(color:green)BUILD SUCCESSFUL\\

Total time: 9 seconds%%

----

''Next Up:'' __Part II:__ [Creating new Managers|CreateManager] - A HowTo for creating Business Facades, which are similar to [Session Facades|http://java.sun.com/blueprints/patterns/SessionFacade.html], but don't use EJBs. These facades are used to provide communication from the front-end to the DAO layer.

Raible's Wiki

AppFuse

Other Applications

CreateDAO_zh