You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/03/18 20:28:44 UTC

[jira] [Commented] (TAP5-1659) PageLink: page parameter should accept page-classes and page-instances

    [ https://issues.apache.org/jira/browse/TAP5-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939681#comment-13939681 ] 

ASF subversion and git services commented on TAP5-1659:
-------------------------------------------------------

Commit 19b3960905197fd5848bc8e0cc8e90379e6ace44 in tapestry-5's branch refs/heads/master from [~thiagohp]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=19b3960 ]

TAP5-1659: PageLink: page parameter should accept page-classes and
page-instances

> PageLink: page parameter should accept page-classes and page-instances
> ----------------------------------------------------------------------
>
>                 Key: TAP5-1659
>                 URL: https://issues.apache.org/jira/browse/TAP5-1659
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>            Reporter: Reinhold Gruber
>            Priority: Minor
>              Labels: pagelink
>
> The page parameter of PageLink does only accept a string. This means that the page containing this PageLink has to know the corresponding logical page name. Accepting a page-class would be more typesafe and refactoring friendly. Further if we could use an injected and propely configured page instance for the page parameter, the PageLink component could easily calculate the activation context from the corresponding onPassivate() method.



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