DatePicker doesn't work when CryptedUrlWebRequestCodingStrategy is in effect
----------------------------------------------------------------------------
Key: WICKET-2231
URL: https://issues.apache.org/jira/browse/WICKET-2231
Project: Wicket
Issue Type: Bug
Components: wicket-datetime
Affects Versions: 1.4-RC2
Reporter: Dominik Drzewiecki
Fix For: 1.4-RC3
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
