If you're index page is supposed to render something and the
parameters are all wrong then you can return a 404 from there. The
strategy that I'm using is to gather up all my parameters in specific
onActivate methods and then the empty param onActivate checks the
context and returns 404 if it's not
On Mon, Jun 7, 2010 at 10:31 AM, Todd Orr wrote:
> This works. However, it is awkward as now I need to specifically refer to my
> start page rather than the directory, somedir/start vs somedir/. I hope this
> is resolved in future releases.
What I do is that I use a Start page at the root level (
Thanks Kalle,
This works. However, it is awkward as now I need to specifically refer to my
start page rather than the directory, somedir/start vs somedir/. I hope this
is resolved in future releases.
On Mon, Jun 7, 2010 at 12:50 PM, Kalle Korhonen
wrote:
> Use a Start page instead of an Index pa
Use a Start page instead of an Index page - the index page treats
everything as the context for the Index page if the string doesn't map
to any other page.
Kalle
On Mon, Jun 7, 2010 at 9:43 AM, Todd Orr wrote:
> I've setup a custom 404 page according to
> http://wiki.apache.org/tapestry/Tapestr
I've setup a custom 404 page according to
http://wiki.apache.org/tapestry/Tapestry5HowToUseTapestryForCustomErrorPages.
However, whenever I navigate to a URL that does not exist Tapestry simply
renders the index page for that directory or a directory above if none
exists in that directory. How do y
