Hello, everyone! On Sun, Jun 11, 2023 at 2:04 PM Vangel V. Ajanovski <ajanov...@gmail.com> wrote:
> This bug prompts another question that bothers me. > > How come nobody else has noticed the bug for two years? I had a report > in Sep 2021, which did not get an answer, there is another mention on > Stack Overflow in the last month and now this thread here opened by Chris. Well, I work with a fairly large project which uses tapestry-hibernate and Hibernate a lot, in both web and non-web (typically, Quartz jobs, but not only that) and I haven't run into this problem yet. > 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), Yeah, it doesn't seem to happen for everyone. tapestry-hibernate has unit and integration tests and they have been successful. > or tapestry-hibernate is not in use any more by > committers and other developers and tapestry-jpa is the preferred way, tapestry-hibernate is in use by the committers. There's no preference for it over tapestry-jpa nor the other way around. > or both are obsolete nowadays and one should pursue some other approach > to persistence when using Tapestry? That's definitely not the case. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
