Hi,

I have an EventLink that triggers an event method on a component nested in a form (formA) and returns a Block with in it another form (formB) to update a zone which is outside formA. Tapestry still complains about formB being nested in formA. This is probably because of the fact that the component that renders formB in the Block to be returned lives inside a formA.

Though slightly odd, this seems to me a valid usecase that should be supported which would mean this is a bug. If I am missing something or am just asking too much of tapestry, please tell me off :) If not, shall I submit a bugreport?

Cheers,
Joost

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

Reply via email to