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

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639252#action_12639252 ] 

Howard M. Lewis Ship commented on TAP5-273:
-------------------------------------------

Tapestry has the tools you need already in place.

Basically, what you want is:

On render: read ProprertyEditContext.propertyValue and expand to multiple local values, with editors for those local values.

On submit: validate and combine those local values into a single value and update PropertyEditContext.propertyValue.

SubmitNotifier gives you part of what you need.  For the moment (until 5.1) you will need to supply another component, inside your property editor Block, and surrounding or before your other fields, to handle the render side.

> Callback in a property editor
> -----------------------------
>
>                 Key: TAP5-273
>                 URL: https://issues.apache.org/jira/browse/TAP5-273
>             Project: Tapestry 5
>          Issue Type: Bug
>            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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org