Java Mailing List Archive

http://www.junlu.com/

Home » Home (12/2007) » J2EE Pattern »

Re: Suggestions welcome

Huy Nguyen

2004-03-24

Replies:

At least do not use Entity Bean for this.
 
DAO would probably be ok for this.
 
-spacemaster

Maya menon <maya_java@YAHOO.COM> wrote:
All,
 
I need help in this situation. We have to develop an enterprise application ( a web site) using J2EE technologies. I was planning to use, Struts and J2EE patterns.
 
Now, it looks like our database will be frequently changing. The changes can include, dropping a field, adding a new field, dropping a table etc.
In this case, which is a good design for handling back end ?
 
I was planning to use Entity bean,facade and Transfer object.
 
How does it sound ?
Thanks

Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time. ==================================================================== 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@java.sun.com



huy.nguyen

(t)+612 9271 3241 (e) d_huy_nguyen@yahoo.com

Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time. ==================================================================== 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@java.sun.com

©2008 junlu.com - Jax Systems, LLC, U.S.A.