[
https://issues.apache.org/jira/browse/TAPESTRY-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geoff Callender reopened TAPESTRY-2169:
---------------------------------------
Thanks for doing ExceptionDisplay, but why not do a component that does ALL the
non-production-mode stuff so we can put it in our own pages with a single line?
eg.
<t:exceptionandsessiondisplay exception="exception"/>
For now we users still have to copy the part that gets the session attributes,
which we may have to keep up-to-date as T5 progresses, eg.
<h1 class="t-exception-report">An unexpected application exception has
occurred.</h1>
<t:exceptiondisplay exception="exception"/>
<div class="t-env-data">
<h2>Request</h2>
<t:renderobject object="request"/>
<t:if test="hasSession">
<h2>Session</h2>
<dl>
<t:loop source="session.attributeNames"
value="attributeName">
<dt>${attributeName}</dt>
<dd>
<t:renderobject
object="attributeValue"/>
</dd>
</t:loop>
</dl>
</t:if>
</div>
> Create an ExceptionAnalysisDisplay component
> --------------------------------------------
>
> Key: TAPESTRY-2169
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2169
> Project: Tapestry
> Issue Type: New Feature
> Affects Versions: 5.0.10
> Reporter: Geoff Callender
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.11
>
>
> Move the guts of ExceptionReport into an ExceptionAnalysisDisplay component
> to enable reuse in our own custom ExceptionReport pages like so:
> <body>
> <t:if test="productionMode">
> <!-- Put our production-happy exception display in here -->
> </t:if>
> <t:unless test="productionMode">
> <!-- Display Tapestry's full-on exception info here -->
> <t:exceptionanalysisdisplay exception="prop:exception"/>
> </t:unless>
> </body>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
