I encountered the same problem in June. If you want to use Wicket 1.3 in Websphere 6, you need to upgrade to Websphere 6.0.2.17 or higher
@see http://www.mail-archive.com/[EMAIL PROTECTED]/msg29692.html Sean On 12/11/07, narup <[EMAIL PROTECTED]> wrote: > > > hello all, > > It seems to be solved, i used WicketFilter in web.xml before with which > websphere had a problem, so for that i changed some settings in websphere > to > deploy the app. though it got deployed with that setting but showed some > weird behavior. > > So i again reverted back to WicketServlet and it again worked fine, so > moral > of the story is websphere doesn't handle filter properly > > >
