[
https://issues.apache.org/jira/browse/RAVE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469521#comment-13469521
]
Anthony Carlucci commented on RAVE-806:
---------------------------------------
I can still see the usefulness in having the stack trace available no matter
what the jsDebugMode flag is set. For example, in a production environment it
will be assumed that flag will be off. However, that might be the most useful
environment to be able to have the stack trace available for tracking down
issues from an enterprise support perspective.
As an alternate solution, I would suggest that we always have the stack trace
always available on the error page, hidden by default, with a "see more
details" button/link that could render it.
Thoughts by the community?
> Show stack trace error or fiendly error message page depending on jsDebugMode
> -----------------------------------------------------------------------------
>
> Key: RAVE-806
> URL: https://issues.apache.org/jira/browse/RAVE-806
> Project: Rave
> Issue Type: Improvement
> Reporter: Daniel Gornstein
> Priority: Minor
> Attachments: friendlyErrorMessagePage(Rave-806).patch
>
>
> If jsDebugMode is on show the stack trace error as rave currently works.
> If jsDebugMode is off show a friendly error message page
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
