I heard that Webspere gets confused with a filter as the endpoint. Try WicketServlet. I think there also is a patch for more recent Websphere versions.
On Sunday, May 1, 2011, drf <davidrfi...@gmail.com> wrote: > I should add that we are using Spring 3, which uses ContextLoaderListener, > not ContextLoaderServlet > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Running-Wicket-under-WebSphere-tp3487476p3487531.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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
