[
https://issues.apache.org/jira/browse/TAPESTRY-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship resolved TAPESTRY-1613.
--------------------------------------------
Resolution: Invalid
Assignee: Howard M. Lewis Ship
You're own example shows why this is not necessary, just name the method
onActionFromTheUniqueId(), or add @OnEvent(component="theUniqueId") to an
existing method. Either way, it's less typing and less configuration, and more
self-documenting, than the T4 approach.
> add an optionnal t:listener to t:actionLink
> -------------------------------------------
>
> Key: TAPESTRY-1613
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1613
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Cyrille
> Assignee: Howard M. Lewis Ship
>
> I think it would be nice to have a optional t:listener to the t:actionLink
> component to bind it's event to the specified method, like T4 do.
> <a href="#" t:type="actionLink" t:id="theUniqueId"
> t:listener="theListenerMethod" t:context="aValue">et voilà</a>
> If it is not a good idea, can you explain why ? It will drive me in the right
> way.
> Thanks to give us Tapestry ! It is a really great and nice tool !!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
