[TAP5-2070] Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4
• Fix Version/s: 5.4
• Component/s: tapestry-core
• Assignee: Massimo Lusetti
• Reporter: Massimo Lusetti
• Created: 10/Feb/13 21:43
• Updated: 27/Aug/13 09:43
• Resolved: 27/Aug/13 09:43

Description

The behavior from day one for pages within Tapestry is to being able to serve requests that come with an activation context with more parameters that the ones declared by the page itself.

This feature lead the framework to serve requests that comes to URL which are not explicitly declared by the pages, for example a page named: Super with an activation event handler method like this one:

onActivate(String character)

{ ... }

will finely serve requests for:

/super/mario
/super/luigi
/super/wario
/super/waluigi

but it will also serve requests for:

/super/mario/luigi/wario/waluigi

This issue is to change that behavior.
If the page does declare a specific activation event handler method the corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is raised.

Issue Links

• supercedes: TAP5-879 404 is never raised automatically if the application has an index page.