Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Date: Fri, 26 Oct 2012 23:39:12 +0000 (UTC)
From: "Paul Stanton (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Message-ID: <822850500.34088.1351294752442.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (TAP5-2021) create compatible client side method
 of encoding context parameters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Paul Stanton created TAP5-2021:
----------------------------------

             Summary: 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


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira