hey,

This is an excellent article, and summarizes some really useful tips. In
a web app with no EJBs especially, you have to be a bit more carfeul
when handling concurrency, transactions etc since your code doesn't run
in the managed environment of the EJB container. So it pays to be extra
careful when designing the model layer and data access.
We have some similiar material in our BluePrints adventure builder
application early access architecture/design document at
http://java.sun.com/blueprints/code/adventure/1.0/docs/architecture.html
where we discuss DAOs and transaction since the adventure builder
highlights a web-centric architecture(no ejbs). Your article really
captures a lot of good advice.

hope that helps,
Sean

Sullivan, Sean C - MWT wrote:

>If you are using the DAO pattern, you may be interested
>in this article.
>
>Advanced DAO Programming
>http://www-106.ibm.com/developerworks/library/j-dao/
>
>-Sean
>
>====================================================================
>Companion Site: http://www.corej2eepatterns.com
>J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
>Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
>
>

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)