You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2014/12/31 01:22:13 UTC

[jira] [Commented] (TAP5-2435) Tapestry's internal pages should always use the packaged version of bootstrap, not any applicaton override

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

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

Much of the support for this is already present ... but the timing isn't working.  

AbstractInternalPage.setupRender() is getting invoked after the @Import attached to ExceptionReport has already forced the core stack into the page.

> Tapestry's internal pages should always use the packaged version of bootstrap, not any applicaton override
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-2435
>                 URL: https://issues.apache.org/jira/browse/TAP5-2435
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> When Tapestry renders the T5Dashboard, or the ExceptionReport pages (internal pages) it should not include the core stack automatically. Instead, these pages should render with the internal stack and not the core stack.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)