[aerogear-dev] [aerogear-controller] Default Error Page

[Matthias Wessendorf]

On Mon, Oct 8, 2012 at 3:16 PM, Douglas Campos <qmx at qmx.me> wrote:
> For now a show details is fine - on the future it would be cool to have a development mode/production mode a la rails/express
>

had the same idea - but was not sure if adding more and more features
blows it (the controller) up


-M

> I'll file the @jira
>
> On Oct 8, 2012, at 10:07 AM, Daniel Bevenius wrote:
>
>> Thanks guys!
>>
>> I like ''show details' and I'll add that to toggle the stacktrace.
>>
>> >i wonder if an option to have it on/off for the developer would be to overkill?
>> 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?
>>
>>
>>
>> On 8 October 2012 14:52, Lucas Holmquist <lholmqui at redhat.com> wrote:
>> looks cool!
>>
>> 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?
>> On Oct 8, 2012, at 8:43 AM, Matthias Wessendorf <matzew at apache.org> wrote:
>>
>> > On Mon, Oct 8, 2012 at 2:39 PM, Daniel Bevenius
>> > <daniel.bevenius at gmail.com> wrote:
>> >> Hi all,
>> >>
>> >> I wanted to get some input on what you'd like to see on a default error page
>> >> in aerogear-controller. This is the page that a user will see if an error
>> >> occurs, and no custom error route has been defined.
>> >> I'm attaching a screenshot of what I'm playing with at the moment.
>> >>
>> >> Some thoughts:
>> >> 1. Should we be showing the stacktrace at all?
>> >
>> > yes
>> >
>> >> 2. Should we have a button which can be used to display the stacktrace?
>> >
>> > that would be nice, to have a button 'show details' (or what ever name)
>> >
>> > -M
>> >
>> >>
>> >> Any suggestions are as always most welcome.
>> >>
>> >> Thanks,
>> >>
>> >> /Daniel
>> >>
>> >> _______________________________________________
>> >> aerogear-dev mailing list
>> >> aerogear-dev at lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> >>
>> >
>> >
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog: http://matthiaswessendorf.wordpress.com/
>> > sessions: http://www.slideshare.net/mwessendorf
>> > twitter: http://twitter.com/mwessendorf
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> -- qmx
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf