You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Johan Compagner (JIRA)" <ji...@apache.org> on 2008/04/09 15:10:24 UTC

[jira] Updated: (WICKET-1501) MarkupCache.putIntoCache doesn't behave correctly!!

     [ https://issues.apache.org/jira/browse/WICKET-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johan Compagner updated WICKET-1501:
------------------------------------

    Fix Version/s: 1.4-M1
                   1.3.4
         Assignee: Johan Compagner  (was: Juergen Donnerstag)

ahh ok so loadMarkup is the method that is incorrect.

I will fix that that putInCache is not called when cache key == null

> MarkupCache.putIntoCache doesn't behave correctly!!
> ---------------------------------------------------
>
>                 Key: WICKET-1501
>                 URL: https://issues.apache.org/jira/browse/WICKET-1501
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.3
>            Reporter: Jan Kriesten
>            Assignee: Johan Compagner
>            Priority: Critical
>             Fix For: 1.3.4, 1.4-M1
>
>
> '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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.