Google for a wicket london weekend presentation and follow up blog on loading jpa entity managers on demand. There have also been various posts relating to using the open session in view Hibernate filter.
The JPA blog entry uses the requestcycle to prepare a thread local. The first call to use it creates the entity manager and keeps it in the thread local. The request cycle end request and exception methods handle the cleanup and close. Very brief description but if you google for the topics above it is all very well explained. HTH Adrian On Mon, Oct 5, 2009 at 6:22 PM, Petr Fejfar <petr.fej...@gmail.com> wrote: > On Mon, Oct 5, 2009 at 5:12 AM, Jeffrey Schneller > <jeffrey.schnel...@envisa.com> wrote: > > > I really don't want to bloat my code to implement Spring but if it is the > only way to do it then I will. > > When I've started learning of Wicket few month ago, my position was > the similiar: I'd like to avoid stuff like Maven, Spring etc... I > found out Databinder as well and tried it. But I was not able to make > it running with Hibernate, just with HSQLDB. > > So we've decided to continue with Spring, Maven... We've increased our > overhead little bit, but once we define beans, we do not care about > them any more. There was only one pitfall: manually invoking injection > of non-visual components. After few month I must say that Spring seems > to be the least problematic part of our projects. > > > Petr > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
