I have had to deal with the infamous WebSphere-servlet-filter-implementation-sucks problem before. As discussed, this requires that the WicketServlet be used instead of the WicketFilter. Ok, no sweat since WicketServlet calls the WicketFilter methods anyway. However, I have a time-critical deliverable so I'll have to live with it. Once that is completed, I plan to open a PMR with IBM about this issue.
I really appreciate your help, guys! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/URL-pattern-app-does-not-work-for-Wicket-1-4-6-and-WebSphere-6-1-tp1891723p2335590.html Sent from the Wicket - User 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
