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 2014/04/04 20:00:24 UTC

[jira] [Closed] (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:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1744.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.4

> 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
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.4
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)