Felix, that's brilliant, thanks a lot, it solved my problem. I had no idea that
request.getParameter and @ActivationRequestParameter use different encoding
schemes.
Thanks
-Original Message-
From: Felix Gonschorek [mailto:fe...@netzgut.net]
Sent: Friday, May 20, 2016 14:11
To: Tapestry
Hello Davide,
you can inject the Request (org.apache.tapestry5.services.Request) service
into your page and then access the parameter with
request.getParameter("myParam")
this should go around the tapestry encoding and type coercing mechanisms.
Felix
2016-05-20 13:57 GMT+02:00 Davide Vecchi :
Hi everybody ,
In order to have a Tapestry page correctly receive an
@ActivationRequestParameter , the value in the querystring must be sent encoded
in the Tapestry way (f.ex. using Tapestry's URLEncoder service), so f.ex. a
space char becomes $0020 , a "&"becomes $0026 etc.
However this encod
