You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by ZiciuM <l6...@rtrtr.com> on 2012/09/11 02:31:32 UTC

Trigerring two events

I get ComponentException and InternalOperationException. I deem possible
reason for such a matter may be found in trigerring two events, and Tap is
confused which one should deal with first, so is there anything that could
prevent or direct such behavior? What should I do?



--
View this message in context: http://tapestry.1045711.n5.nabble.com/Trigerring-two-events-tp5716177.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

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


Re: Trigerring two events

Posted by Muhammad Gelbana <m....@gmail.com>.
I can only think about 2 different requests after reading your question but
I really think this can be done using one event. I suggest you fire a third
event that triggers your 2 existing event handlers as normal java methods.
I assume only one of the existing methods could be returning something.

Some code will be very helpful.

On Tue, Sep 11, 2012 at 2:31 AM, ZiciuM <l6...@rtrtr.com> wrote:

> I get ComponentException and InternalOperationException. I deem possible
> reason for such a matter may be found in trigerring two events, and Tap is
> confused which one should deal with first, so is there anything that could
> prevent or direct such behavior? What should I do?
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Trigerring-two-events-tp5716177.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>