On Wed, 17 Oct 2012 10:36:46 -0300, George Christman
<gchrist...@cardaddy.com> wrote:
So I think this is my last question in regards to this topic. If your
doing your calculations on the fly, example converting aston marton to
aston-martin which would mean you would later need to convert it back to
aston marton to do the query, what do you do when the string naturally
contains a dash. Example blue-purple, no spaces, but when decoded it
would be decoded as blue purple with the assumption we replace dashes
with space.
This is some logic you need to do yourself.
If I go the encoder route, I'd probably want something that handles all
my parameter strings. It would be nice if tapestry offered you the
ability to easily change it's encoder strategy. Example uses dashes
instead of the
zeros.
There is already: override the URLEncoder service. Or override the default
ValueEncoder for String, as Lance suggested.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
