[
https://issues.apache.org/jira/browse/WICKET-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702848#action_12702848
]
Igor Vaynberg commented on WICKET-2180:
---------------------------------------
the fix is committed into 1.3.x branch, but the build candidate i created did
not include it. will wait to see what happens with the build. if the build is
voted this will go into 1.3.7, if the build needs to be rebuilt then this will
make it into 1.3.6 redox.
the fix has also been comitted into trunk
> WicketSessionFilter assumes that the WicketFilter has already been inited
> -------------------------------------------------------------------------
>
> Key: WICKET-2180
> URL: https://issues.apache.org/jira/browse/WICKET-2180
> 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.
