You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jan Kriesten (JIRA)" <ji...@apache.org> on 2008/04/09 10:27:27 UTC
[jira] Commented: (WICKET-1501) MarkupCache.putIntoCache doesn't
behave correctly!!
[ https://issues.apache.org/jira/browse/WICKET-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587093#action_12587093 ]
Jan Kriesten commented on WICKET-1501:
--------------------------------------
I don't actually understand why the markup is loaded from the markupCache in putIntoCache at all - it's already provided as a method argument...
> 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
> Priority: Critical
>
> '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.