Also, with filters, you can add in as many as you like for different purposes. With the request cycle, you either have to hand-code the logic into the request cycle implementation or develop a pluggable architecture where you can add more things in dynamically, but then you're right back to where you were in the first place with filters. So, I concur with Daniel; filters are not hacks.
On Wed, Sep 17, 2008 at 3:19 PM, Daniel Freitas <[EMAIL PROTECTED]> wrote: > I wouldn't classify filters as hacks. I like to think about them as > primitive forms of AOP. Unless you think about AOPs as hacks :P... > > 2008/9/17 mmocnik <[EMAIL PROTECTED]> > >> >> Thanks a lot, thats exactly what I was looking for. >> I overwrote newRequestCycle() in my Application to return my own >> WebRequestCycle subclass. >> >> I was allready wondering if that really wasn't possible to do without some >> hack with a filter. >> >> Thanks again, >> Marko >> >> >> igor.vaynberg wrote: >> > >> > subclass webrequestcycle and put your stuff into onbeginrequest. >> > >> > -igor >> > >> >> -- >> View this message in context: >> http://www.nabble.com/How-to-execute-something-on-the-very-beginning-of-the-request-cycle-tp19527780p19535006.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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]
