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

MarkupCache.putIntoCache doesn't behave correctly!!

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.3.3
    • Fix Version/s: 1.3.4, 1.4-M1
    • Component/s: wicket
    • Labels:
      None

      Description

      'putIntoCache' checks for the locationString not to be null instead of the cacheKey!

      This way you always get old markup returned instead of the freshly supplied markup which shouldn't be cached at all.

        Attachments

          Activity

            People

            • Assignee:
              jcompagner Johan Compagner
              Reporter:
              jkriesten Jan Kriesten
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: