On Wed, Jun 21, 2017 at 1:42 AM, abangkis wrote:
> I was thinking because of how the Services implementation & instantiation
> is managed by tapestry. How the service is injected instead of manually
> created.
>
> Thanks for the hint, I will look at those files source code.
>
Hi Cezary,
Thanks, exactly what I needed.
As I am creating the link with the url parameter in another Tapestry
application I can just use the URLEncoder.encode() method.
Op 20/06/2017 om 21:57 schreef Cezary Biernacki:
Tapestry uses its own encoding (with $ used as escape + four hex digits
Hey,
I was using @ActivationRequestParameter as I need it to be a part of
activation/passivation so it does not get lost when changing language
for example.
Using Request.getParameter() does work, but then I'm not sure how to use
activation/passivation exactly.
But as Cezary said in