Re: [Tapestry-developer] question about binding

[Howard M. Lewis Ship]

Form components respond to the submission in the order that they render.  It looks like your Submit component renders before your PropertySelection component, therefore the Submit's listener is notified before the PropertySelection gets a chance.   You may want to have the Submit component's listener just set a flag, and have the Form's listener (which is notified dead last), perform whatever operation is appropriate. ----- Original Message ----- From: xuzhou To: tapestry-developer Sent: Wednesday, September 18, 2002 11:33 PM Subject: [Tapestry-developer] question about binding Hi all,   I use Form to developer my own component. There are one Submit and one PropertySelection in this form. The submit has its listener and the propertySelection's value is bound to property path(it's java class's field). In listener, there are codes to modify this field.   When the submit button is pushed, i found the listener mothod is executed firstly, then the property path is bound, i.e. this field value is modifidy by the listener firstly, then by the binding mechanism. I think the property path should be bound firstly. I am not sure whether the tapestry's problem or i make some mistakes.   Thanks.