On Sun, Jan 27, 2013 at 10:25 PM, Kalle Korhonen <kalle.o.korho...@gmail.com > wrote:
> > > My typical pattern is don't use Index pages, use servlet standard error > code mapping to Tapestry error pages, e.g: > > <error-page> > <error-code>401</error-code> > <location>/error401</location> > </error-page> > <error-page> > <error-code>404</error-code> > <location>/error404</location> > </error-page> > I want exactly the same, but I want to be able to use Index as I remember, for example, that the Start page is somehow deprecated in flavor of Index ones... Someone correct me if I'm wrong. > > I use Tynamo's tapestry-routing (http://tynamo.org/tapestry-routing+guide) > for "folder-specific" index pages, e.g: > @At("/") > public class Home {...} > > I've always found Tapestry's Index page handing to be too far reaching. > I don't want to use something "external" to achieve this. I think it should be part of the standard page handling/processing mechanism. Now I'm thinking about a way to reach the goal without changing the "semantic" of page request handling cause now if you have an index page with: void onActivate(String test) { System.out.println("first context parameter: " + test); } if I call the url: /first/second/third ... My activation context method is called with the first parameter and the other discarded... My vision is that this should result in a 404. What do you think? -- Massimo
