You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2016/02/22 14:45:20 UTC

[jira] [Updated] (TAP5-1932) Exposing the Link in the EventLink component

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

Jochen Kemnade updated TAP5-1932:
---------------------------------
    Labels: bulk-close-candidate  (was: )

This issue affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent version of Tapestry (currently 5.4.0, available from Maven Central), please update it as soon as possible and add '5.4.0') to the issue's affected versions.

> Exposing the Link in the EventLink component
> --------------------------------------------
>
>                 Key: TAP5-1932
>                 URL: https://issues.apache.org/jira/browse/TAP5-1932
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3.3
>            Reporter: Steve Eynon
>            Priority: Trivial
>              Labels: bulk-close-candidate
>         Attachments: Link.patch
>
>
> I would like to alter the Link in an EventLink via a Mixin - specifically, remove the LoopBack parameter.
> To do this, the "AbstractLink.link" field needs to be set *before* the link is rendered and a simple change to org.apache.tapestry5.corelib.base.AbstractComponentEventLink would accomplish this:
>  protected void setupRender() {
>    super.link = createLink(context);
>  }
> AbstractLink.link would also need to become protected.
> I believe the above to be a small yet useful enhancement to the Link Component API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)