A few people have suggested using a filter to handle the hibernate session. It probably wouldn't be a bad idea to see such a filter in the source for hibernate users. Any contributors?
Callbacks are another feature that would be trivial to handle given the "views aren't terminal" idea that, um, probably isn't workable. :) --------------------------------------------------------- Joseph B. Ottinger [EMAIL PROTECTED] http://enigmastation.com IT Consultant On Fri, 8 Nov 2002, Gavin King wrote: > Is there some feature of WebWork that allows an application to perform some > cleanup code after rendering a view? Many of our users need some way to > close/commit the Hibernate session/transaction *after* the view is rendered. > The reason for this is that Hibernate might return lazy-initializing proxies > and collections (when configured to do so in the OR mapping). So its > necessary for the session/transaction to remain open while the view is being > rendered, since some data might be transaparently retrieved from the > database during rendering. > > I am adding this problem to our FAQ and I would like to be able to tell > people a simple best-practice solution for WebWork.... > > Thanks > > Gavin > http://hibernate.sourceforge.net > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
