You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Gabriel H. Lozano M." <ga...@edesa.net> on 2006/01/04 15:27:07 UTC
strange order of submit
Hi everyone
I have this problem: I have an imageSubmit with a listener, inside a form
without a listener. I have a propertySelection inside the form. When I clic
on the submit image first it is calling the listener and next it sets the
object of the property selection. I know this because I print when the
property selection models sets the selected object. Is this correct?? Is
this the correct way things should go??
Gabriel Lozano.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: strange order of submit
Posted by "Gabriel H. Lozano M." <ga...@edesa.net>.
I am using tapestry 3.0.3., so I solved in a different way, in the listener
of the image submit I set a Boolean property that later I read. Thanks
anyway, it will be very useful because I am planning to use the imageSubmit
everywhere.
-----Mensaje original-----
De: Robert Zeigler [mailto:robertz@scazdl.org]
Enviado el: Miércoles, 04 de Enero de 2006 09:38 a.m.
Para: Tapestry users
Asunto: Re: strange order of submit
What version of tapestry are you using? In 3.0.3, things are called in
the order in which they appear on the form, so if your image submit
appears before your property selection, then this is the correct
behavior. If you're using 4.x, things change slightly. The listener
parameter is still notified as in 3.0.3. But you can also specify (or
you can specify instead) an "action" (also a listener method). The
action is called at the end of the form rewind, just before the form
listener. So, if you're using 4.x, try using the action parameter rather
than the listener parameter.
Robert
Gabriel H. Lozano M. wrote:
> Hi everyone
>
> I have this problem: I have an imageSubmit with a listener, inside a form
> without a listener. I have a propertySelection inside the form. When I
clic
> on the submit image first it is calling the listener and next it sets the
> object of the property selection. I know this because I print when the
> property selection models sets the selected object. Is this correct?? Is
> this the correct way things should go??
>
> Gabriel Lozano.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: strange order of submit
Posted by Robert Zeigler <ro...@scazdl.org>.
What version of tapestry are you using? In 3.0.3, things are called in
the order in which they appear on the form, so if your image submit
appears before your property selection, then this is the correct
behavior. If you're using 4.x, things change slightly. The listener
parameter is still notified as in 3.0.3. But you can also specify (or
you can specify instead) an "action" (also a listener method). The
action is called at the end of the form rewind, just before the form
listener. So, if you're using 4.x, try using the action parameter rather
than the listener parameter.
Robert
Gabriel H. Lozano M. wrote:
> Hi everyone
>
> I have this problem: I have an imageSubmit with a listener, inside a form
> without a listener. I have a propertySelection inside the form. When I clic
> on the submit image first it is calling the listener and next it sets the
> object of the property selection. I know this because I print when the
> property selection models sets the selected object. Is this correct?? Is
> this the correct way things should go??
>
> Gabriel Lozano.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org