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 starting). I'm assuming this is a bug ? I would have expected tapestry to handle it automatically...
For now I can get around it by doing a URLEncoder.encode on it when I set it. The funny thing is that it seems to automatically decode by itself, because I never actually decode it. So I need to manually encode it for every response. Thanks, Ryan -- View this message in context: http://tapestry.1045711.n5.nabble.com/T5-3-ActivationRequestParameter-not-encoding-to-be-URL-friendly-tp5024732p5024732.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
