why would that be a problem for wicket the urls of wicket don't point to any files directly. But there are a lot of those (struts .do files??) so it seems that it first tries to resolve a jsp file before giving it to the filter? But how is that relevant for wicket? what does it first try to resolve? If that is the case that a filter only works for a request that maps to a real file then that websphere version should never be released. That seems to me like a major critical bug.
but you can always use the wicket servlet. johan On 6/8/07, Sean Sullivan <[EMAIL PROTECTED]> wrote:
Websphere 6.0.2.13 returns a 404 response for all of my requests. The root cause seems to be a bug in Websphere's servlet container. The bug is documented here: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PK27620 I'm the process of upgrading to Websphere 6.0.2.17. I'll let you know if the problem goes away. Sean On 6/8/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote: > > > > Sean Sullivan-3 wrote: > > > > FYI --- I'm still having serious trouble with Wicket 1.3 in Websphere > 6.0. > > I am debugging the issue and > > I'll open a JIRA issue this morning. > > > > Sean > > > > What issues are you having ? > We are running Wicket 1.3 on WebSphere 6 (using OSGI BridgeServlet). > > Jan. > >
