On Mon, 19 Nov 2007 14:19:28 -0200, lasitha <[EMAIL PROTECTED]>
wrote:
On Nov 19, 2007 5:42 PM, Thiago H de Paula Figueiredo
<[EMAIL PROTECTED]> wrote:
Hi, Lasitha! (By the way, where are you from?)
Oh, the beautiful town of kandy, sri lanka :)
I'm from the not so beautiful city of Belo Horizonte, Minas Gerais state,
Brazil. :)
In the meantime, may i ask whether/how HiberTapestry solves the
problem posed in this thread? To wit: hibernate will detect and commit
changes to dirty objects even if we've realized mid way through the
unit-of-work that it should be rejected.
I havent't noticed this problem before. Until now, HiberTapestry opens a
transaction when a service method annotated with @Transactional is invoked
and commits it when the method finishes without exceptions. Otherwise, the
transaction is aborted.
The Spring OSIV filter/interceptor avoids this problem by turning off
automatic session flushing and relying on service layers to explicitly
commit (either manually or declaratively)[2].
See paragraph above. :)
--
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]
