Re: Suggestions welcome

Message

We solve simmilar problem in the following way:

We use DAO patterm with TO where DAO hide the DB access and its API provides TO that carry the data between entities. In this case you main interaces will not change when you add or remove fields. The overhead in this case is that you always fetch from DB all the data relevant for the TO. I think that this is minor overhead.

Aaron

-----Original Message-----
From: An interest list for Sun Java Center J2EE Pattern Catalog [mailto:J2EEPATTERNS-INTEREST@JAVA.SUN.COM] On Behalf Of Maya menon
Sent: Wednesday, March 24, 2004 11:54 PM
To: J2EEPATTERNS-INTEREST@JAVA.SUN.COM
Subject: Suggestions welcome

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

==================================================================== 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

Re: Suggestions welcome

Aaron Tubman

2004-03-25