Re: Calling method after CommitAfter call

[g kuczera <gk...@gmail.com>]

Guys, I forgot to tell you that since applying the
"HibernateSessionManager.commit()" everything works like a charm. It looks
that it was indeed the problem with synchronisation.

2016-02-26 13:14 GMT+01:00 Thiago H de Paula Figueiredo <th...@gmail.com>
:

> On Fri, 26 Feb 2016 07:54:47 -0300, g kuczera <gk...@gmail.com> wrote:
>
> But I feel quite ashamed of this solution. It's like forcing the inner
>> mechanism of Tapestry's Hibernate Wrapper (or even the Hibernate by
>> itself,
>> it's flow) to commit the thing before it is appropriate.
>>
>
> I disagree. Tapestry-Hibernate is a thin wrapper to begin with. What
> you're doing is very normal usage of both Tapestry and Hibernate.
>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>