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 where it is harder to use the filter - for example weblogic has pretty broken filter support, also some osgi containers only support registration of servlets. -igor On Jan 10, 2008 11:44 AM, Beyonder Unknown <[EMAIL PROTECTED]> wrote: > > 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 is change. > > > > > > ____________________________________________________________________________________ > Be a better friend, newshound, and > know-it-all with Yahoo! Mobile. Try it now. > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > > > --------------------------------------------------------------------- > 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]
