[jira] [Closed] (TAP5-1820) Default Exception Report Page should have a link to discard component class loader and retry

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

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

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

       Resolution: Fixed
    Fix Version/s: 5.4

In development mode, the exception report now includes a number of options to reload the page and/or discard caches and loaded component classes.

> Default Exception Report Page should have a link to discard component class loader and retry
> --------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1820
>                 URL: https://issues.apache.org/jira/browse/TAP5-1820
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: exception-reporting
>             Fix For: 5.4
>
>
> Sometimes you attempt to reach a page, but it doesn't exist because of a syntax error.
> Even after you create the page and reload, Tapestry may not pick up the change because it is not monitoring the directory containing the .class file, because it didn't successfully load a file from that directory.
> It would be nice if the exception report page included a link to discard the class loader, forcing a reload of the page(s) for the request, and would then redirect back to the page (or event request) that failed.
> Caveats:
> - Different handling for an Ajax request, where the class loader should be discarded, and a response returned that will dismiss the exception report iframe.
> - POST requests may be tricky.
> - The link should only appear if the request is white-listed (by default, from localhost).



--
This message was sent by Atlassian JIRA
(v6.1#6144)