My general approach is to use query parameters, not context info in the path, for any dynamic portions of a query from the client.
On Fri, Oct 31, 2008 at 7:43 AM, Martijn Brinkers <[EMAIL PROTECTED]> wrote: > The latest build (5.0.16) comes with a new URLBuilder. The problem I now > have is that some AJAX'ified javascripts suddenly stops working because > the context now contains illegal characters (for example the @ symbol of > an email address). I therefore need to encode the parameters before > building the context URL. As some of these parameters contain the Id of > a DOM object I cannot just convert these parameters before calling the > javascript function because sometimes they will be used to get the value > of a control (using their id). I therefore need to encode the parameters > in javascript. Is there already a Tapestry URL encoder for Javascript (I > mean the Tapestry proprietary URL encoder)? > > Thanks, > > Martijn Brinkers > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
