You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Marius Siegas <in...@gmail.com> on 2004/10/02 08:03:27 UTC

Re: SubmitListener

In your Submit listeners you could mark which of them is activated and
do processing according to that mark later in your Form listener.


On Thu, 30 Sep 2004 08:42:39 +0200, Eric Fesler <er...@audaxis.com> wrote:
> Hi,
> 
> I 'm a newbie with Tapestry and I recently came into what seems to be a
> classical issue.
> 
> I have a page with Submit components and listener for that components.
> Depending upon the position of the Submit components (at the beginning
> of the form or at the end of the form) I hved a completely different
> behavior.
> 
> Looking deeper, I found that it was due to the fact that submit listener
> are triggered at the time the component is rewind and that explained the
> problem.
> 
> I looked for some discussions on the subject and I found the following
> page on the wiki.
> http://tapestry.sourceforge.net/wiki/index.php/Developer%20Issues
> This page mentions that "Howard initiated a discussion on how the
> listeners could be improved to make their use more natural to
> developers." but there isn't any pointer to such a discussion.
> 
> Is there any place where I could find discussion to this issue?
> 
> I'm looking for a way to be able to trigger different actions (based on
> the clicked button or image) *after* the form has been fully rewind.
> 
> Any suggestions?
> 
> Thanks,
> 
> --ERic

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org