Hi Ben,
Thank you for your investigative efforts, even though you weren't yet
able to pinpoint the exact cause. And thank you, you and Vangel, for
sharing that workaround.
Occasionally, this HibernateCrudServiceDAO method works as expected.
Most times not. This seeming randomness fits with your explanation of
the 'shadow Session' being generated at runtime... perhaps something is
prematurely getting garbage collected?
For now, I'll switch to session.getSession() as suggested. I guess this
returns an actual Hibernate session, bypassing Tapestry's per-thread
(scope) logic in between.
Should this issue be recorded as a potential bug so that it eventually
gets fixed?
Kind regards,
Chris.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
