Hi Vangel > Is this because the bug only occurs in some very specific environments > (only some specific OS and some specific JDK combination and some > specific DB driver), or tapestry-hibernate is not in use any more by > committers and other developers and tapestry-jpa is the preferred way, > or both are obsolete nowadays and one should pursue some other approach > to persistence when using Tapestry?
We have two Tapestry apps in production. One uses tapestry-hibernate, but is still on Tapestry 5.5, so out of the scope of the problem you described. The other one uses tapestry-jpa, therefore also not relevant. I think both work very well, at least for us, but I acknowledge others, including you, are experiencing difficulties in some setups. Keen to find the cause and fix it. Thanks, Volker --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
