[
https://issues.apache.org/jira/browse/TAPESTRY-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2432.
------------------------------------------
Resolution: Won't Fix
Assignee: Howard M. Lewis Ship
I think you can accomplish what you need with the bulit-in SubmitNotifier
component. It fires events before and after the components in its body are
activated to process a submission.
> Callback in a property editor
> -----------------------------
>
> Key: TAPESTRY-2432
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2432
> Project: Tapestry
> Issue Type: Improvement
> Components: Core Components
> Affects Versions: 5.0.12
> Reporter: José Paumard
> Assignee: Howard M. Lewis Ship
>
> 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.
-
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]
