Please note an alternative is the tapestry-jpa module, which you could support
with hibernate or any other implementation of JPA.
Another alternative is to not use either and use standard Java EE Session Beans
instead, as indeed I usually do.
> On 13 Jan 2016, at 8:49 PM, Ido Dovrat wrote:
>
On Wed, 13 Jan 2016 10:49:41 -0200, Ido Dovrat
wrote:
Hibernate is not a dependency of Tapestry. The integration is provided
as a separate module. There is no surefire way to make such a module
compatible across all version combinations (tapestry and hibernate).
Agreed, even if I underst
Hibernate is not a dependency of Tapestry. The integration is provided as a
separate module. There is no surefire way to make such a module compatible
across all version combinations (tapestry and hibernate).
I think tapestry-hibernate should always be aligned with the latest version
of Hibernate
Hi Kalle, hi all!
I migrated to Hibernate 4.2.8 and everything works fine.
Nevertheless I want to open a discussion about the current persistence
layer integration of T5.4, if I am allowed to.
I do not believe an UI Framework should force users to upgrade a
persistence layer to a particular ve
