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 (Updated) (JIRA)" <ji...@apache.org> on 2011/12/30 20:28:31 UTC

[jira] [Updated] (TAP5-1809) Option to render a particular page instance in its current state (without page activation)

     [ https://issues.apache.org/jira/browse/TAP5-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-1809:
---------------------------------------

    Issue Type: New Feature  (was: Sub-task)
        Parent:     (was: TAP5-1808)
    
> Option to render a particular page instance in its current state (without page activation)
> ------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1809
>                 URL: https://issues.apache.org/jira/browse/TAP5-1809
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.4
>            Reporter: Howard M. Lewis Ship
>
> Tapestry 5.2 introduced StreamPageContent as a return value from @Traditional event handler methods.  It requires the event handler method to return not just the page class, but the activation context for the page, and the page is activated before being used to stream the result.
> This is not always desirable; in many cases, the page to be rendered has already been activated and possibly, the code desiring the activation does not know the page activation context for the desired page.  Changing StreamPageContent's constructor and API to support (render as-is, without forcing page activation) is desirable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira