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

[jira] [Updated] (TAP5-13) @Mixin should accept parameters

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

Jochen Kemnade updated TAP5-13:
-------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, 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 development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> @Mixin should accept parameters
> -------------------------------
>
>                 Key: TAP5-13
>                 URL: https://issues.apache.org/jira/browse/TAP5-13
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.2
>            Reporter: Dan Adams
>              Labels: bulk-close-candidate
>
> With @Mixin there is no way to use a mixin that requires parameters within a component. For instance if you have a Confirm mixin that has a required parameter you can't use it like this:
> @Mixin
> private Confirm confirm;



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