Thank you Thiago, I use that too, but I am trying to de-couple the DAO implementation from the underlaying database access. Then I would be able to re-use my module (with its DAOs) with any other data access technology.
Regards, Matías. Thiago H. de Paula Figueiredo wrote: > > Em Mon, 11 Jan 2010 17:20:46 -0200, matias.blasi <matias.bl...@gmail.com> > escreveu: > >> Anyway, I am thinking on developing some business components, as tapestry >> modules, which should interact with the underlying database, but I don't >> want to couple them with neither hibernate nor anyone database >> technology, so, I am thinking which is the most standard way to make it >> abstract. > > There is one and its widely used: the Data Access Object design pattern > (DAO). I use and recommend. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, software architect and developer, Ars Machina Tecnologia da > Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > -- View this message in context: http://old.nabble.com/Is-tapestry-coupled-with-Hibernate-API--tp27111015p27126916.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
