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

WicketSessionFilter assumes that the WicketFilter has already been inited

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 1.3.6, 1.4-RC3
    • 1.3.6
    • wicket
    • 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

          is a clone of

          Bug - A problem which impairs or prevents the functions of the product. WICKET-2180 WicketSessionFilter assumes that the WicketFilter has already been inited

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. WICKET-2151 WicketSessionFilter doesn't takes into account WebApplication#getSessionAttributePrefix(WebRequest)

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              ivaynberg Igor Vaynberg
              drzewo Dominik Drzewiecki
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: