Thanks guys!<div><br></div><div>I like '<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">'show details' and I'll add that to toggle the stacktrace. </span></div>
<div><font color="#222222" face="arial, sans-serif"><br></font></div><div>>i wonder if an option to have it on/off for the developer would be to overkill?<font color="#222222" face="arial, sans-serif"><br></font>I'm thinking that during development one could simply leave out an error route, and then later, add a custom error route for general/specific error in which case the developer provides his/her own error page and can choose what they'd like to show their users. Does that sound reasonable?</div>
<div><br></div><div><br></div><div><br><div class="gmail_quote">On 8 October 2012 14:52, Lucas Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">looks cool!<br>
<br>
i like the idea of having a show/hide toggle for the stacktrace. i wonder if an option to have it on/off for the developer would be to overkill?<br>
<div class="HOEnZb"><div class="h5">On Oct 8, 2012, at 8:43 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
<br>
> On Mon, Oct 8, 2012 at 2:39 PM, Daniel Bevenius<br>
> <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:<br>
>> Hi all,<br>
>><br>
>> I wanted to get some input on what you'd like to see on a default error page<br>
>> in aerogear-controller. This is the page that a user will see if an error<br>
>> occurs, and no custom error route has been defined.<br>
>> I'm attaching a screenshot of what I'm playing with at the moment.<br>
>><br>
>> Some thoughts:<br>
>> 1. Should we be showing the stacktrace at all?<br>
><br>
> yes<br>
><br>
>> 2. Should we have a button which can be used to display the stacktrace?<br>
><br>
> that would be nice, to have a button 'show details' (or what ever name)<br>
><br>
> -M<br>
><br>
>><br>
>> Any suggestions are as always most welcome.<br>
>><br>
>> Thanks,<br>
>><br>
>> /Daniel<br>
>><br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> Matthias Wessendorf<br>
><br>
> blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
> sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
> twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div>