You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/07/25 02:07:49 UTC

[jira] [Commented] (TAP5-1744) Returning a StreamPageContent instance from any of a Form's events results in "Form components may not be placed inside other Form components" exception

    [ https://issues.apache.org/jira/browse/TAP5-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719067#comment-13719067 ] 

Howard M. Lewis Ship commented on TAP5-1744:
--------------------------------------------

I may look at another solution, where we use the informaton collected from event handler method's return value, but instead of acting on it immediately, back out of the current Environment and start the new render clean.
                
> Returning a StreamPageContent instance from any of a Form's events results in "Form components may not be placed inside other Form components" exception
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1744
>                 URL: https://issues.apache.org/jira/browse/TAP5-1744
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.4, 5.2
>            Reporter: Howard M. Lewis Ship
>
> At the time the event is triggered, the FormSupport (and other stuff) is in the Environment. The new page render occurs INSIDE the same environment, causing errors when the new render of the Form tries to store its own FormSupport into the Environment.
> The solution is to use Environment.cloak() and decloak() around the new render.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira