wicket-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johan Compagner" <jcompag...@gmail.com>
Subject Re: About WicketFilter refactoring
Date Sat, 03 Feb 2007 22:37:32 GMT
just use string.indexOf() ;)

johan


On 2/3/07, Igor Vaynberg <igor.vaynberg@gmail.com> wrote:
>
> we already have a pull parser in wicket, why arent we using that?
>
> -igor
>
>
> On 2/3/07, Eelco Hillenius <eelco.hillenius@gmail.com> wrote:
> >
> > > Therefore I suggest to compute the  filter path in a static block,
> > > as web.xml  is not supposed to  change during the lifetime  of the
> > > app, nor between initialization of the various WicketFilters.
> >
> > Usually, using static backfires in some way or the other.
> >
> > I think wicket-example's startup time is still reasonable, though a
> > lot slower for sure. An optimization could be to use SAX parsing
> > rather then DOM. With a static block, I would be afraid to introduce
> > classloader problems for some setups (even if it is against the spec
> > etc); this way of parsing the web.xml pretty much guarantees that will
> > never happen.
> >
> > My 2c,
> >
> > Eelco
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message