[ https://issues.apache.org/jira/browse/TAP5-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046848#comment-14046848 ]
Paul Stanton commented on TAP5-2021: ------------------------------------ that would make the event parameter wiring non-interchangeable if used by multiple methods of invocation - not to mention ugly... anyway, it is a simple script which i have written/tested and will just have to carry around to each tapestry project i work on. > 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)