That's odd, it seems like most situations could be known by tapestry already. It does know what pages (and thus page packages) exists, so why couldn't it just know that if a valid package but invalid page is requested, then it should fail instead of passing it as an activation context?
Anyway, thanks for your help :) sincerely, chris lewis kranga wrote: > Oddly enough using Start instead of Index handles this situation > correctly. > > ----- Original Message ----- From: "Lutz Hühnken" > <[EMAIL PROTECTED]> > To: "Tapestry users" <users@tapestry.apache.org> > Sent: Thursday, July 31, 2008 5:16 AM > Subject: Re: T5: index page in pages package acts as a catchall > > >> Dear Chris, >> >>> Ends up as http://app.com/. Am I doing something wrong? Surely others >>> have run into this and deem it undesirable, no? >> >> yes and yes. It has been discussed on this list before and a >> workaround (that works well for me) has been proposed. You can see the >> thread here: >> http://www.nabble.com/Index-page-context-and-404-response-to16649174.html#a16649174 >> >> >> Described very roughly: >> >> Assuming your index page is not meant to be called with parameters - >> if parameters are given, the user was probably actually requesting a >> non-existing page. So if index is called with parameters, reply with a >> 404 not found. >> >> Hth, >> >> Lutz >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://thegodcode.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
