WicketSessionFilter assumes that the WicketFilter has already been inited
-------------------------------------------------------------------------
Key: WICKET-2243
URL: https://issues.apache.org/jira/browse/WICKET-2243
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.3.6, 1.4-RC3
Reporter: Dominik Drzewiecki
Assignee: Igor Vaynberg
Priority: Critical
Fix For: 1.3.6, 1.4-RC3
The patch applied for issue 2151 breaks things. According to the servlet specs,
the order in which container initializes filters is undefined.
WicketSessionFilter assumes that the appropriate wicket filter serving wicket
application has already been inited. This is particularly noticeable on
WebSphere AppServer 6.1 (6.1.0.19), while on Tomcat 6.0 and 5.5 runs fine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
