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.
On Mon, Jun 19, 2017 at 7:22 PM, Thiago H. de Paula Figueiredo <
On Tue, Jun 20, 2017 at 1:12 PM, Nathan Quirynen <
nat...@pensionarchitects.be> wrote:
> Hi,
>
> I have a page that needs to accept an url as query or context parameter.
>
> So for example: https://abc.com?redirectUrl=https://def.com/abc123/456
>
> But Tapestry does not accept the slashes (even
Tapestry uses its own encoding (with $ used as escape + four hex digits
unicode) for URLs, see org.apache.tapestry5.services.URLEncoder and
implementation org.apache.tapestry5.internal.services.URLEncoderImpl
Hi,
I have a page that needs to accept an url as query or context parameter.
So for example: https://abc.com?redirectUrl=https://def.com/abc123/456
But Tapestry does not accept the slashes (even if I use the %2F notation):
*Input string '[...]' is not valid; the character '/' at position 7 is
Hello Tapestry users,
I'd like to share a small library that we use to manage & validate
configuration symbols for Tapestry5 application:
https://github.com/anjlab/anjlab-tapestry-commons/tree/master/anjlab-tapestry-config
README with some examples available by above link.
--
Dmitry Gusev
