Francois Armand wrote:
So, if (as it's in my case) you use onActivate(String name) in a page
using a post, the "name" given to onActivate for the post action will
receive a non decoded String. If some validation are done based on
that encoded value, as a check in DB, they fail.
So, as I figur
Hello,
I'm still stick with some encoding issue for URL using UTF-8.
I'm stick with Tapestry 5.0.6. I applied the patch for TAPESTRY- bug (
https://issues.apache.org/jira/secure/attachment/12371922/context_encode_decode_fix_to_5.0.6.patch),
what solves a lot of problem.
But it's not over, an