This is quite a pesky problem. I tried going w/ the Start page approach mentioned in https://issues.apache.org/jira/browse/TAP5-879?attachmentOrder=desc ; however, as it appears the approach w/ Start pages no longer works (and they're deprecated anyway). It certainly is a surprise when the app never returns a 404 and always sends the user to the index page, but it's not a terrible surprise as the user gets to see a real page with content .
I'll look forward to the 5.4 solution. Cheers, Alex K On Mon, Aug 20, 2012 at 9:36 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > 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-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > >
