i already said OSIV that comes with spring doesnt support transaction-per-request, so what makes you think i am using it or any other filter? :) wicket has plenty of hooks to do this.
-igor On Thu, Mar 26, 2009 at 3:36 PM, James Carman <jcar...@carmanconsulting.com> wrote: > On Thu, Mar 26, 2009 at 6:32 PM, Igor Vaynberg <igor.vaynb...@gmail.com> > wrote: >> not if you buffer the response like wicket does by default :) > > Right, but you have to make sure your filters fire in the correct > order, then. If your OSIV wraps around WicketFilter, then buffering > won't fix the problem. The exception will happen after Wicket's done. > Right? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
