> > How come nobody else has noticed the bug for two years? > In general we're isolating the use of Tapestry to our presentation layer - The datastore access (and business logic) lives in modules and the UI sits on top of the business logic layer - The lower level modules are usually wired up with Spring IoC and we bridge the two IoC systems, so Tapestry can see/inject Spring services, but the opposite is not true.
With a traditional layering like that we never need to access the datastore directly from Tapestry code - so a lot of the magic Tapestry modules/features are not in play (like hibernate integration etc). -- Chris On Sun, Jun 11, 2023 at 7: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. > > 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? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
