[
https://issues.apache.org/jira/browse/WICKET-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587155#action_12587155
]
Jan Kriesten commented on WICKET-1501:
--------------------------------------
Johan -
I return 'null' for the cacheKey of my template. That's fine. The Markup isn't
cached _under_this_ key.
The problem arises because wicket caches the Markup in putIntoCache also under
the locationString - which has nothing to do with the cacheKey. So, markup is
cached under two keys by wicket, which leads to the problem.
Regards, --- Jan.
> 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: Juergen Donnerstag
> 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.
