On Mon, 20 Aug 2012 19:18:30 -0300, Howard Lewis Ship <hls...@gmail.com>
wrote:
I'm considering a change for Tapestry 5.4 where the ValueEncoder,
responsible for converting portions of the URL into the page
activation context, will have a new method that defines what it
expects to see in its portion of the URL, in terms of a regular
expression.
Shouldn't we have a different encoder specific for URLs (with ValueEncoder
as a fallback) and leave ValueEncoder more focused on dealing with form
fields? This way, we can handle this validation without changing
ValueEncoder.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
