yes, and hivetranse seem to be doing it the right way. http://hivetranse.sourceforge.net/
I think the long session pattern is coming to hivetranse soon. On 9/23/05, Schulte Marcus <[EMAIL PROTECTED]> wrote: > No, we don't use Spring anymore. I was (probably quite unjustified) a bit > fed up with Spring after our first Session per request experiences. Now we > use Hivemind whose concept of a "service-model" I found very appealing. > > > > -----Original Message----- > > From: Pete [mailto:[EMAIL PROTECTED] > > Sent: Friday, September 23, 2005 8:41 AM > > To: Tapestry users > > Subject: Re: Hibernate session model > > > > > > You really convince me that session-per-request is history... > > > > are you also using spring for transactions / resource > > handling / hibernate > > templates? > > > > > > On Fri, 23 Sep 2005 08:23:23 +0200, Schulte Marcus > > <[EMAIL PROTECTED]> > > wrote: > > > > > We're using using long sessions in two productive apps now. > > It works > > > great > > > and, for us, simplifies development considerably. Our first > > app using > > > hibernate used Spring w/ session per request and it > > generated some really > > > nasty ad-hoc work-around-code. > > > > > > We've implemented the long-session Pattern as a Hivemind > > service-model > > > which > > > was really easy to do. > > > > > > hth, > > > Marcus > > > > > >> -----Original Message----- > > >> From: Henri Dupre [mailto:[EMAIL PROTECTED] > > >> Sent: Thursday, September 22, 2005 9:25 PM > > >> To: Tapestry users > > >> Subject: Hibernate session model > > >> > > >> > > >> Has anyone implemented a different Hibernate session > > model than the > > >> per-request with Tapestry? > > >> We are currently using a per-request one (with the Spring Hibernate > > >> filter) but I'm considering a per-websession model (store the > > >> Hibernate session in the Visit). We are running into some complex > > >> LazyExceptions and I don't see any advantage of using a per-session > > >> model. > > >> Any experiences? > > >> > > >> Thanks, > > >> > > >> Henri. > > >> > > >> > > --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > >> For additional commands, e-mail: > > [EMAIL PROTECTED] > > >> > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- /ted --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
