[jira] [Closed] (TAP5-2244) T5.4 tapestry-core integration test app3/renderpagedemo exhibits shady requirejs behavior

["Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>]

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

Thiago H. de Paula Figueiredo closed TAP5-2244.
-----------------------------------------------

    Resolution: Not a Problem

This is not actually a problem. As Jochen said, the rendered page ends up having two pieces of page JS initialization because a whole page is included inside the other. That page is just to show what can be done with PageDocumentGenerator and easily see that it renders a whole page to a Document and from it to a String. Anyway, I've changed the page inclusion from OutputRaw (unfiltered) to ${} expansion (filtered), which avoids any JS exceptions.

> T5.4 tapestry-core integration test app3/renderpagedemo exhibits shady requirejs behavior
> -----------------------------------------------------------------------------------------
>
>                 Key: TAP5-2244
>                 URL: https://issues.apache.org/jira/browse/TAP5-2244
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Chris Poulsen
>
> The error can be seen by  firing up the app3 from an editor and visiting /renderpagedemo  - The console error is: "TypeError: require is not a function".
> From the page source it seems that all the javascript for requirejs configuration/initialization is included twice in the page.
> This error can also be reproduced using the adjustments from TAP5-2239



--
This message was sent by Atlassian JIRA
(v6.2#6252)