Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-2180

WicketSessionFilter assumes that the WicketFilter has already been inited

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.4-RC3
    • Component/s: wicket
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ivaynberg Igor Vaynberg
                Reporter:
                drzewo Dominik Drzewiecki
              • Votes:
                1 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: