[WICKET-2231] DatePicker doesn't work when CryptedUrlWebRequestCodingStrategy is in effect

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4-RC2
• Fix Version/s: 1.4-RC3
• Component/s: wicket-datetime
• Assignee: Juegen Donnerstag
• Reporter: Dominik Drzewiecki
• Created: 21/Apr/09 11:44
• Updated: 26/Apr/09 17:07
• Resolved: 26/Apr/09 17:07

Description

With CryptedUrlWebRequestCodingStrategy, when url rewriting is the effective session tracking mechanism, the ResourceReference for the wicket-date.js is rendered incorrectly, as it bears the crypted target, but the key to decrypt this piece of information is not referable, as it is kept in the session, which in turn cannot be resolved as had been stripped from the generated url just before being put into the map of variables to be interpolated with DatePicker.js. As a resolution, a single call to Strings.stripJSessionId() should be removed.