We also had similar problems on WAS 6.1 and we also used Wicket Servlet to mitigate our issues.
We've been preparing for an upgrade of our servers, mostly comparing WebSphere 7 and WebSphere 8. V7 seems to behave the same as V6.1 whereas V8 seems to handle the Wicket Filter much better. On Mon, Jan 23, 2012 at 1:49 PM, Andrew Geery <andrew.ge...@gmail.com>wrote: > I've had a very similar problem with WAS 6.1 (basic functionality would > work but AJAX functionality did not). The solution was simply to use the > Wicket servlet instead of the filter -- see > https://cwiki.apache.org/WICKET/websphere.html. What made it hard to > debug > was the fact that the Wicket filter implementation did work for aspects on > WAS, but it didn't work for AJAX calls. > > HTH > Andrew > > On Mon, Jan 23, 2012 at 12:23 PM, matteus <matteu...@hotmail.com> wrote: > > > > > Yes, my application is running with the filter Wicket Filter. > > > > -- > > View this message in context: > > > http://apache-wicket.1842946.n4.nabble.com/Wicket-websphere-7-tp4310810p4321364.html > > Sent from the Users forum mailing list archive at Nabble.com. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > -- Sent by Eric Hamel
