On Fri, 08 Oct 2010 04:07:16 -0300, ael <alan-lua...@dash.com.ph> wrote:
So what would be the difference?
The important is you achieve
what you want to do.
The difference is that the Tapestry-Hibernate integration (session and
transaction handling) will not work if your DAO is not a Tapestry-IoC
service. That simple.
As Howard said, you don't need to use Tapestry-Hibernate. If you don't,
then you need to handle sessions and transactions yourself.
It's very important to achieve, but the way you achieve is is very
important too. Messed up code, even when it works, has less value, as the
only 100% sure thing in software development is that something will
change. With well-written code, reacting to this changes is way faster,
easier and needs less effort.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, 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
