Hello Thiago,
thanks for your answer.
The idea was to only use tapestry-ioc which is supposed to be usable as
an isolated component with no dependency to tapestry-core.
tapestry-hibernate, however, depends on tapestry-core, according to
Hi!
Indeed, almost every Tapestry-IoC service is only created when first used.
In other words, lazily.
On Mon, May 8, 2017 at 10:57 AM, yazmin georgina quintal <
geolit...@yahoo.com.mx.invalid> wrote:
> Thank you for your interest.
> I found the contribution was called asyncronously when
Hello!
Why don't you just use tapestry-hibernate to let it deal with creating and
handling Hibernate sessions?
https://tapestry.apache.org/using-tapestry-with-hibernate.html
Also, I believe your code may not be incorrect, but it's not good. Unless
you want only one Hibernate session for the
Thank you for your interest.
I found the contribution was called asyncronously when needed, no during app
initialization... so I was wrong.
Saludos.
Atte. Yazmín Georgina Quintal Moo
Local 63 y 64 de Plaza de la Tecnología. Villahermosa, Tab.
Tel 993 1311688
Cel. 9931 689207
De:
