> Hmm... there is just one, no more. :( You have run into a known Glassfish bug where WicketFilter.init() is called twice. A solution is to add a boolean "guard" in a WicketFilter subclass that only calls super.init() once.
- Tor Iver
> Hmm... there is just one, no more. :( You have run into a known Glassfish bug where WicketFilter.init() is called twice. A solution is to add a boolean "guard" in a WicketFilter subclass that only calls super.init() once.
- Tor Iver