Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3779931 By: gpviz1
It seems that bug # DISPL-12 was fixed in release 1.0 RC2. However, in Display Tag version 1.1 the fix does not seem to be there (if I understood correctly how the fix was implemented). I am still getting the behavior reported in the bug, where the algorithm in the ParamEncoder class produces some non-unique keys (ex, using the id input "child36" produces the same key as "child43"). In looking at the suggested fix, the suggestion seemed to be to use the prime number 37 in the algorithm. But the code in the class that I have (again, release 1.1) looks identical to the code in release 1.0 and uses the prime number 3. Is there something I'm missing here? Either way I'm still getting the non-unique keys issue... (The title of the original bug was "Algorithm in org.displaytag.util.ParamEncoder is bogus".) Thanks! -Gary ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=249318 _______________________________________________ displaytag-user mailing list displaytag-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-user
