[jira] [Closed] (TAP5-757) Allow PageLink's "page" parameter to accept page instance or class instead of just logical name to add new type-safe way of render request generation

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade closed TAP5-757.
-------------------------------

    Resolution: Not a Problem

Another year has passed since the last comment. Therefore, we assume this issue has either been resolved in the meantime or it is no longer relevant to you.
If recent versions of Tapestry (i.e. 5.4 betas and 5.3.7) are still affected, please reopen the issue and adjust the "Affected Version/s" property.

> Allow PageLink's  "page" parameter to accept page instance or class instead of just logical name to add new type-safe way of render request generation
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-757
>                 URL: https://issues.apache.org/jira/browse/TAP5-757
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Vjeran Marcinko
>              Labels: bulk-close-candidate
>
> It's a bit overkill to use ActionLink only for render requests (when no action is needed) just to use its ability to return target page instance from handler methods, preconfigured with required context values. This type safety comes at the expense of 2 HTTP requests.
> If PageLink's "page" parameter could not only accept logical page name, but also page instance, then it would be possible to achieve same type-safety with only one HTTP request.



--
This message was sent by Atlassian JIRA
(v6.2#6252)