Wicket
  1. Wicket
  2. WICKET-3931

Component markup caching inconsistencies

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5-RC5.1
    • Fix Version/s: 1.5-RC6
    • Component/s: wicket
    • Labels:
      None

      Description

      In WICKET-3891 we found that Component#markup field is not being reset between requests. The problem is that this field is transient and it is null-ified only when the page is read from the second level page cache (see https://cwiki.apache.org/confluence/x/qIaoAQ). If the page instance is read from first level cache (http session) then its non-serialized version is used and the markup field value is still non-null.

      In WICKET-3891 this looked like a minor issue with the markup caching in development mode but actually this problem is valid even in production mode.
      See the attached application. When the panel's variation is changed every MarkupContainer inside still uses its old markup.

      1. variation.tgz
        21 kB
        Martin Grigorov
      2. WICKET-3931.patch
        4 kB
        Martin Grigorov
      3. WICKET-3931.patch
        3 kB
        Martin Grigorov

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Martin Grigorov
              Reporter:
              Martin Grigorov
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development