Re: WicketServlet vs. WicketFilter

2008-01-11 Thread Igor Vaynberg
yes there is some overhead. but it is much better then the servlet. the filter can let the resource fall through and be served by the servlet cotainer. if you use a servlet then the servlet itself has to stream the resource out. guess which will have a more optimized implementation... -igor On J

Re: WicketServlet vs. WicketFilter

2008-01-11 Thread Eelco Hillenius
On Jan 11, 2008 5:33 PM, Maris Orbidans <[EMAIL PROTECTED]> wrote: > > > also wicket filter is much better at handling /* mapping > > > The only problem with this mapping is that filter is invoked for all > requests that fetch static web resources (css, images, etc). > I may be wrong but I don't th

Re: WicketServlet vs. WicketFilter

2008-01-11 Thread Maris Orbidans
also wicket filter is much better at handling /* mapping The only problem with this mapping is that filter is invoked for all requests that fetch static web resources (css, images, etc). I may be wrong but I don't think it's good for performance. Especially if you use some other filter, f

Re: WicketServlet vs. WicketFilter

2008-01-11 Thread Joshua Jackson
I think it's Websphere: http://joshuajava.wordpress.com/2007/11/12/my-first-impression-about-wicket/ On 1/11/08, Gwyn Evans <[EMAIL PROTECTED]> wrote: > On 10/01/2008, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > example weblogic has pretty broken filter support, > > Wasn't that Websphere rather t

Re: WicketServlet vs. WicketFilter

2008-01-11 Thread Gwyn Evans
On 10/01/2008, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > example weblogic has pretty broken filter support, Wasn't that Websphere rather than Weblogic, or did I miss something? /Gwyn - To unsubscribe, e-mail: [EMAIL PROTECTED]

Re: WicketServlet vs. WicketFilter

2008-01-10 Thread Beyonder Unknown
Thanks Igor! I understand it now. Best, WT -- The only constant in life is change. - Original Message From: Igor Vaynberg <[EMAIL PROTECTED]> To: users@wicket.apache.org Sent: Thursday, January 10, 2008 11:48:04 AM Subject: Re: WicketServlet vs. WicketFilter sometimes you

Re: WicketServlet vs. WicketFilter

2008-01-10 Thread Igor Vaynberg
sometimes you might want to chain preprocessors/postprocessors around wicket - in that case you have to use filters since you cant chain servlets. also wicket filter is much better at handling /* mapping generally i would recommend wicketfilter. wicketservlet is there as a backup for situations w

WicketServlet vs. WicketFilter

2008-01-10 Thread Beyonder Unknown
Hi All, Are there any criteria in choosing WicketFilter over WicketServlet? In the api it says, "Please use WicketFilter if you require advanced chaining of resources". What does this mean? If you have deeply rooted Panel within a Panel with a Panel? Thanks, WT -- The only constant in life