On Tue, 20 Nov 2007 02:02:18 -0200, lasitha <[EMAIL PROTECTED]>
wrote:
Yes. But my question pertains more to the span of the hibernate
_session_ than to that of the transaction.
A typical OSIV implementation keeps a single session open right until
the end of a request so the view layer can access entities loaded in
that request without having to worry about lazy-loading exceptions and
such.
HiberTapestry follows the OSIV pattern. The difference with
tapestry-hibernate is that HiberTapestry just opens a transaction when a
@Transactional-annotated service method is invoked.
If, otoh, it does keep a session open, does it flush the session at
the end of the request?
At the end of a @Transactional-annotated service method that initiated a
transaction, if no exception was thrown, the transaction is commited and,
as a consequence, flushed. Otherwise, it is rolled back.
Thanks for keeping up this thread - once i can look at your source i
will bother you less :)
I'm just polishing it and adding more unit tests before I show my little
creation for the world to see. :) Or you're not bothering me at all. :)
--
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]
