[ https://issues.apache.org/jira/browse/WICKET-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587179#action_12587179 ]
Jan Kriesten commented on WICKET-1501: -------------------------------------- That's what I was trying to say: Even though cacheKey is 'null' - the markup is still cached under locationString. Since the resulting Markup is always returned from 'putIntoCache' - the originally updated markup in the parameter to 'putIntoCache' is thrown away and replaced by the old cached one... 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.