Tapestry should be smarter about event handler methods refiring events with the
same name
-----------------------------------------------------------------------------------------
Key: TAPESTRY-1920
URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
Project: Tapestry
Issue Type: New Feature
Components: tapestry-core
Reporter: Howard M. Lewis Ship
An idiom that's evolving is for a component or mixin to receive an event via an
event handler method, and then refire the event with a different context to
obtain information or behavior from its container.
Currently, you must either a) fire a differently named event or b) expressly
trigger the event on the container's resources.
It would be nice if Tapestry was smarter, and woul track which event(s) a
component or mixin is currently handling, and would automatically skip the
component if another event of the same name was triggered. Basically, roll the
b) logic above directly into ComponentResources/ComponentPageElement.
--
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]
