[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728527#comment-13728527
]
Hudson commented on TAP5-2070:
------------------------------
FAILURE: Integrated in tapestry-trunk-freestyle #1123 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/1123/])
TAP5-2070 annotation and service response handler to get access to page with
exact activation context (mlusetti: rev
8fecc8e18e46919387dae2683ebc231f6beb1a74)
*
tapestry-core/src/main/java/org/apache/tapestry5/annotations/UnknownActivationContextCheck.java
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/services/UnknownActivationContextHandler.java
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/services/meta/UnknownActivationContextExtractor.java
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/services/UnknownActivationContextHandlerImpl.java
TAP5-2070 have the component model be able to declare if it handle the
activation context (mlusetti: rev 5cc984b2c826e619d1dcdb52704bdffca263a97e)
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/model/MutableComponentModelImpl.java
TAP5-2070 declare if the component handle the activation context (mlusetti: rev
8640a40fdd25f23bd071fcb627ab31cac8670ca7)
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/transform/OnEventWorker.java
TAP5-2070 publish new method to let other code check for activation context
handling (mlusetti: rev 3054fd6ee8ec8c3e8936838c5512780c84ea8598)
* 54_RELEASE_NOTES.txt
*
tapestry-core/src/main/java/org/apache/tapestry5/model/MutableComponentModel.java
* tapestry-core/src/main/java/org/apache/tapestry5/model/ComponentModel.java
TAP5-2070 have the meta data constants used to check each page's value
(mlusetti: rev 2db059c086ca5999889c3b06f4852cf491e5f78b)
* tapestry-core/src/main/java/org/apache/tapestry5/MetaDataConstants.java
TAP5-2070 hook the services into our IoC (mlusetti: rev
6d70228460b0229aa106da356e98ba31ca0ecb36)
* tapestry-core/src/main/java/org/apache/tapestry5/modules/TapestryModule.java
* tapestry-core/src/main/java/org/apache/tapestry5/modules/InternalModule.java
TAP5-2070 check each page for UnknownActivationContext annotation (mlusetti:
rev d1fabecccf7bd81d0dae8eefda055cf02ee4f981)
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/services/DefaultRequestExceptionHandler.java
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ComponentEventImpl.java
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/pageload/PageLoaderImpl.java
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/services/PageActivatorImpl.java
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/structure/ComponentPageElementImpl.java
*
tapestry-core/src/main/java/org/apache/tapestry5/internal/pageload/ComponentAssemblerImpl.java
TAP5-2070 test case to be expanded to use something different then Selenium
since it doesn't check http status code (mlusetti: rev
6762367c1f0369814089f3c0babdc93f71238094)
*
tapestry-core/src/test/java/org/apache/tapestry5/internal/services/ComponentEventImplTest.java
*
tapestry-core/src/test/java/org/apache/tapestry5/internal/structure/ComponentPageElementImplTest.java
*
tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/Index.java
TAP5-2070 actual test pages (mlusetti: rev
c13ed06021cf280ba43b7cd6053ca88da8230b55)
*
tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/UnknownActivationContextDemo.java
*
tapestry-core/src/test/groovy/org/apache/tapestry5/integration/app1/UnknownActivationContextTests.groovy
*
tapestry-core/src/test/resources/org/apache/tapestry5/integration/app1/pages/UnknownActivationContextDemo.tml
> Respond with a HTTP 404 if the page is activated with an activation context
> not explicitly supported by the page itself
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-2070
> URL: https://issues.apache.org/jira/browse/TAP5-2070
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Massimo Lusetti
> Assignee: Massimo Lusetti
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
