You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org> on 2014/06/28 14:26:24 UTC

[jira] [Closed] (TAP5-2021) create compatible client side method of encoding context parameters

     [ https://issues.apache.org/jira/browse/TAP5-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thiago H. de Paula Figueiredo closed TAP5-2021.
-----------------------------------------------

    Resolution: Not a Problem

Use query parameters instead.

> create compatible client side method of encoding context parameters
> -------------------------------------------------------------------
>
>                 Key: TAP5-2021
>                 URL: https://issues.apache.org/jira/browse/TAP5-2021
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Paul Stanton
>            Assignee: Howard M. Lewis Ship
>              Labels: urlencoder
>
> Currently there is no (provided) way to replicate the tapestry propriety URL encoding.
> See org.apache.tapestry5.internal.services.URLEncoderImpl.encode(String)
> This can be limiting for advanced users wiring up custom components which may create requests via javascript.
> I personally have come up against this a number of times.
> I propose that tapestry.js include a function which does the equivalent of URLEncoder.encode, or even better, ComponentResources.createEventLink etc.



--
This message was sent by Atlassian JIRA
(v6.2#6252)