Re: [T5.3] @ActivationRequestParameter not encoding to be URL friendly

2011-11-28 Thread Josh Canfield
commands, e-mail: [hidden email] >> >> > >> > >> >> --------------------- >> To unsubscribe, e-mail: [hidden email] >> >> For additional commands, e-mail: [hidden ema

Re: [T5.3] @ActivationRequestParameter not encoding to be URL friendly

2011-11-28 Thread Kartweel
ubscribe, e-mail: [hidden email] > > For additional commands, e-mail: [hidden email] > > > > > ---------------- > If you reply to this email, your message will be added to the > discussion below: > http://tapestr

Re: [T5.3] @ActivationRequestParameter not encoding to be URL friendly

2011-11-28 Thread Josh Canfield
Looks like a defect, not sure if it's been filed yet. ActivationRequestParameterWorker isn't encoding the client value returned by the ValueEncoder. String clientValue = encoder.toClient(value); link.addParameter(parameterName, clientValue); addParameter is documented as not doing the encodin

[T5.3] @ActivationRequestParameter not encoding to be URL friendly

2011-11-26 Thread Kartweel
Hi, I have a situation where my ActivationRequestParameter has an & symbol in it. This doesn't seem to get encoded when it is attached to the query string. When it gets submitted back to tapestry everything after the & is just truncated (because obviously after the & it thinks a new parameter is st