You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/07/08 02:18:19 UTC

[jira] [Updated] (TAP5-273) Callback in a property editor

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

Howard M. Lewis Ship updated TAP5-273:
--------------------------------------

    Assignee:     (was: Howard M. Lewis Ship)

> Callback in a property editor
> -----------------------------
>
>                 Key: TAP5-273
>                 URL: https://issues.apache.org/jira/browse/TAP5-273
>             Project: Tapestry 5
>          Issue Type: Improvement
>            Reporter: José Paumard
>
> One point a property editor is made is to edit complex properies, that span over serveral basic components : textfields, selects etc... 
> So a parameter is injected in the property editor, edited or created, then taken back by T5, probably to be set in a bean editor. 
> It would be useful to have an event fired in the property editor component, after all the setters have been called, and before the parameter is red by T5. That would allow to build this parameter in a robust way, with the insurance that all the fields have been properly set. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira