tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From José Paumard (JIRA) <...@tapestry.apache.org>
Subject [jira] Reopened: (TAPESTRY-2432) Callback in a property editor
Date Wed, 01 Oct 2008 10:31:44 GMT

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

José Paumard reopened TAPESTRY-2432:

Putting a submit notifier in the TML of the property editor indeed fires the two events in
the associated Java class, but the two events are fired before the setters of the subproperties
are called (it's clearly seen in the logs). So no chance is given to cleanly set the property
handled by this property editor (which needs the subproperties) before it is red by T5. Having
it seems essential to me. 

I could workaround that by putting flags in the different setters and check when I'm in the
last that has been called, and the build the property at that time, but it really not the
cleanest way to use !

> 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

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

View raw message