[WICKET-1501] MarkupCache.putIntoCache doesn't behave correctly!!

• 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
• Assignee: Johan Compagner
• Reporter: Jan Kriesten
• Created: 09/Apr/08 08:09
• Updated: 09/Apr/08 13:16
• Resolved: 09/Apr/08 13:16

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.