On Mon, 19 Nov 2007 16:41:09 -0200, Ezra Epstein <[EMAIL PROTECTED]>
wrote:
I imagine that if you use Spring's declarative transactions on the
service layer so that the read()/get() method does not start a
read/write transaction but the save() method does then changing the
object without calling "save()" should just work - you won't be in a
read/write tx and so the changes to the object won't be persisted. I
haven't tested this.
HiberTapestry works similarly to Spring's declarative transactions,
opening a transaction when a method is invoked and closing it when it
finishes (commit or rollback, depending on whether the invoked method
raised an exception of not).
--
Thiago H. de Paula Figueiredo
Desenvolvedor, Instrutor e Consultor de Tecnologia
Eteg Tecnologia da Informação Ltda.
http://www.eteg.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
