On Mon, Oct 8, 2012 at 2:39 PM, Daniel Bevenius <daniel.bevenius(a)gmail.com&gt; 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(a)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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

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(a)redhat.com&gt; 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(a)apache.org&gt; wrote: > On Mon, Oct 8, 2012 at 2:39 PM, Daniel Bevenius > <daniel.bevenius(a)gmail.com&gt; 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(a)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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

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? 2. Should we have a button which can be used to display the stacktrace? Any suggestions are as always most welcome. Thanks, /Daniel <ErrorPage.png>_______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

I had the same thought but we should be careful. We don't want our error pages to be "too pretty" unless they can be customized based on the data type requested by the client. We have to keep mobile in mind and we don't want to be using a ton of data just to throw big fancy error pages at the app, especially if it's an AJAX request or data being sent over a websocket and it won't even be displayed. In that instance, less would be more. On Oct 8, 2012, at 8:13 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: > What about asking our design overlords (cough James Cobb cough) about it? This is something that if we do right, will help a lot to improve mindshare (beautiful error pages and consistent l&f). > > > On Oct 8, 2012, at 9:39 AM, Daniel Bevenius 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? >> 2. Should we have a button which can be used to display the stacktrace? >> >> Any suggestions are as always most welcome. >> >> Thanks, >> >> /Daniel >> <ErrorPage.png>_______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > -- qmx > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

But that's what I'm saying. For example, say my app is trying to authenticate via a REST endpoint. I haven't specified an error page but auth fails and a 401 is returned. Since it's just a REST call, I don't want an error page but just some JSON back. I just want to make sure that is possible. On Oct 8, 2012, at 8:19 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: > I mean default error page, when the user doesn't specify one. > > On Oct 8, 2012, at 10:17 AM, Kris Borchers wrote: > >> I had the same thought but we should be careful. We don't want our error pages to be "too pretty" unless they can be customized based on the data type requested by the client. We have to keep mobile in mind and we don't want to be using a ton of data just to throw big fancy error pages at the app, especially if it's an AJAX request or data being sent over a websocket and it won't even be displayed. In that instance, less would be more. >> >> On Oct 8, 2012, at 8:13 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >> >>> What about asking our design overlords (cough James Cobb cough) about it? This is something that if we do right, will help a lot to improve mindshare (beautiful error pages and consistent l&f). >>> >>> >>> On Oct 8, 2012, at 9:39 AM, Daniel Bevenius 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? >>>> 2. Should we have a button which can be used to display the stacktrace? >>>> >>>> Any suggestions are as always most welcome. >>>> >>>> Thanks, >>>> >>>> /Daniel >>>> <ErrorPage.png>_______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> -- qmx >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > -- qmx > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

But that's what I'm saying. For example, say my app is trying to authenticate via a REST endpoint. I haven't specified an error page but auth fails and a 401 is returned.

Since it's just a REST call, I don't want an error page but just some JSON back. I just want to make sure that is possible. On Oct 8, 2012, at 8:19 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: > I mean default error page, when the user doesn't specify one. > > On Oct 8, 2012, at 10:17 AM, Kris Borchers wrote: > >> I had the same thought but we should be careful. We don't want our error pages to be "too pretty" unless they can be customized based on the data type requested by the client. We have to keep mobile in mind and we don't want to be using a ton of data just to throw big fancy error pages at the app, especially if it's an AJAX request or data being sent over a websocket and it won't even be displayed. In that instance, less would be more. >> >> On Oct 8, 2012, at 8:13 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >> >>> What about asking our design overlords (cough James Cobb cough) about it? This is something that if we do right, will help a lot to improve mindshare (beautiful error pages and consistent l&f). >>> >>> >>> On Oct 8, 2012, at 9:39 AM, Daniel Bevenius 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? >>>> 2. Should we have a button which can be used to display the stacktrace? >>>> >>>> Any suggestions are as always most welcome. >>>> >>>> Thanks, >>>> >>>> /Daniel >>>> <ErrorPage.png>_______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> -- qmx >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > -- qmx > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Oct 8, 2012, at 8:26 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > On Mon, Oct 8, 2012 at 3:22 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: >> But that's what I'm saying. For example, say my app is trying to authenticate via a REST endpoint. I haven't specified an error page but auth fails and a 401 is returned. > > > > 401 != error But I thought this was for any error without a defined custom route, not just 500. Maybe I'm confused though.

> > 500 ==> error (+ stack trace) > > -M > > >> Since it's just a REST call, I don't want an error page but just some JSON back. I just want to make sure that is possible. >> >> On Oct 8, 2012, at 8:19 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >> >>> I mean default error page, when the user doesn't specify one. >>> >>> On Oct 8, 2012, at 10:17 AM, Kris Borchers wrote: >>> >>>> I had the same thought but we should be careful. We don't want our error pages to be "too pretty" unless they can be customized based on the data type requested by the client. We have to keep mobile in mind and we don't want to be using a ton of data just to throw big fancy error pages at the app, especially if it's an AJAX request or data being sent over a websocket and it won't even be displayed. In that instance, less would be more. >>>> >>>> On Oct 8, 2012, at 8:13 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>>> >>>>> What about asking our design overlords (cough James Cobb cough) about it? This is something that if we do right, will help a lot to improve mindshare (beautiful error pages and consistent l&f). >>>>> >>>>> >>>>> On Oct 8, 2012, at 9:39 AM, Daniel Bevenius 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? >>>>>> 2. Should we have a button which can be used to display the stacktrace? >>>>>> >>>>>> Any suggestions are as always most welcome. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> /Daniel >>>>>> <ErrorPage.png>_______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> -- qmx >>>>> >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> -- qmx >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

You right, this is for any error. Let me look into this and try it out, and make sure that this works. Thx On 8 October 2012 15:30, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > On Mon, Oct 8, 2012 at 3:28 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: > > > > On Oct 8, 2012, at 8:26 AM, Matthias Wessendorf <matzew(a)apache.org&gt; > wrote: > > > >> On Mon, Oct 8, 2012 at 3:22 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: > >>> But that's what I'm saying. For example, say my app is trying to > authenticate via a REST endpoint. I haven't specified an error page but > auth fails and a 401 is returned. > >> > >> > >> > >> 401 != error > > > > But I thought this was for any error without a defined custom route, > not just 500. Maybe I'm confused though. > > > correct - I am not awake :) > > > > > >> > >> 500 ==> error (+ stack trace) > >> > >> -M > >> > >> > >>> Since it's just a REST call, I don't want an error page but just some > JSON back. I just want to make sure that is possible. > >>> > >>> On Oct 8, 2012, at 8:19 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: > >>> > >>>> I mean default error page, when the user doesn't specify one. > >>>> > >>>> On Oct 8, 2012, at 10:17 AM, Kris Borchers wrote: > >>>> > >>>>> I had the same thought but we should be careful. We don't want our > error pages to be "too pretty" unless they can be customized based on the > data type requested by the client. We have to keep mobile in mind and we > don't want to be using a ton of data just to throw big fancy error pages at > the app, especially if it's an AJAX request or data being sent over a > websocket and it won't even be displayed. In that instance, less would be > more. > >>>>> > >>>>> On Oct 8, 2012, at 8:13 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: > >>>>> > >>>>>> What about asking our design overlords (cough James Cobb cough) > about it? This is something that if we do right, will help a lot to improve > mindshare (beautiful error pages and consistent l&f). > >>>>>> > >>>>>> > >>>>>> On Oct 8, 2012, at 9:39 AM, Daniel Bevenius 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? > >>>>>>> 2. Should we have a button which can be used to display the > stacktrace? > >>>>>>> > >>>>>>> Any suggestions are as always most welcome. > >>>>>>> > >>>>>>> Thanks, > >>>>>>> > >>>>>>> /Daniel > >>>>>>> <ErrorPage.png>_______________________________________________ > >>>>>>> aerogear-dev mailing list > >>>>>>> aerogear-dev(a)lists.jboss.org > >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>>>>> > >>>>>> -- qmx > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> aerogear-dev mailing list > >>>>>> aerogear-dev(a)lists.jboss.org > >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> aerogear-dev mailing list > >>>>> aerogear-dev(a)lists.jboss.org > >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>>> > >>>> -- qmx > >>>> > >>>> > >>>> _______________________________________________ > >>>> aerogear-dev mailing list > >>>> aerogear-dev(a)lists.jboss.org > >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev > >>> > >>> > >>> _______________________________________________ > >>> aerogear-dev mailing list > >>> aerogear-dev(a)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(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > _______________________________________________ > > aerogear-dev mailing list > > aerogear-dev(a)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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev >

Created https://issues.jboss.org/browse/AEROGEAR-515 to track this issue. Thanks for all the comments! On 8 October 2012 15:37, Daniel Bevenius <daniel.bevenius(a)gmail.com&gt;wrote: > Actually, qmx just informed me that this will not work at the moment. > I'll create a Jira for this so that this requirement is not lost though. > > > > On 8 October 2012 15:32, Daniel Bevenius <daniel.bevenius(a)gmail.com&gt;wrote: > >> You right, this is for any error. >> >> Let me look into this and try it out, and make sure that this works. >> >> Thx >> >> On 8 October 2012 15:30, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >> >>> On Mon, Oct 8, 2012 at 3:28 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: >>> > >>> > On Oct 8, 2012, at 8:26 AM, Matthias Wessendorf <matzew(a)apache.org&gt; >>> wrote: >>> > >>> >> On Mon, Oct 8, 2012 at 3:22 PM, Kris Borchers <kris(a)redhat.com&gt; >>> wrote: >>> >>> But that's what I'm saying. For example, say my app is trying to >>> authenticate via a REST endpoint. I haven't specified an error page but >>> auth fails and a 401 is returned. >>> >> >>> >> >>> >> >>> >> 401 != error >>> > >>> > But I thought this was for any error without a defined custom route, >>> not just 500. Maybe I'm confused though. >>> >>> >>> correct - I am not awake :) >>> >>> >>> > >>> >> >>> >> 500 ==> error (+ stack trace) >>> >> >>> >> -M >>> >> >>> >> >>> >>> Since it's just a REST call, I don't want an error page but just >>> some JSON back. I just want to make sure that is possible. >>> >>> >>> >>> On Oct 8, 2012, at 8:19 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>> >>> >>> >>>> I mean default error page, when the user doesn't specify one. >>> >>>> >>> >>>> On Oct 8, 2012, at 10:17 AM, Kris Borchers wrote: >>> >>>> >>> >>>>> I had the same thought but we should be careful. We don't want >>> our error pages to be "too pretty" unless they can be customized based on >>> the data type requested by the client. We have to keep mobile in mind and >>> we don't want to be using a ton of data just to throw big fancy error pages >>> at the app, especially if it's an AJAX request or data being sent over a >>> websocket and it won't even be displayed. In that instance, less would be >>> more. >>> >>>>> >>> >>>>> On Oct 8, 2012, at 8:13 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>> >>>>> >>> >>>>>> What about asking our design overlords (cough James Cobb cough) >>> about it? This is something that if we do right, will help a lot to improve >>> mindshare (beautiful error pages and consistent l&f). >>> >>>>>> >>> >>>>>> >>> >>>>>> On Oct 8, 2012, at 9:39 AM, Daniel Bevenius 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? >>> >>>>>>> 2. Should we have a button which can be used to display the >>> stacktrace? >>> >>>>>>> >>> >>>>>>> Any suggestions are as always most welcome. >>> >>>>>>> >>> >>>>>>> Thanks, >>> >>>>>>> >>> >>>>>>> /Daniel >>> >>>>>>> <ErrorPage.png>_______________________________________________ >>> >>>>>>> aerogear-dev mailing list >>> >>>>>>> aerogear-dev(a)lists.jboss.org >>> >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>>>>> >>> >>>>>> -- qmx >>> >>>>>> >>> >>>>>> >>> >>>>>> _______________________________________________ >>> >>>>>> aerogear-dev mailing list >>> >>>>>> aerogear-dev(a)lists.jboss.org >>> >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>>>> >>> >>>>> >>> >>>>> _______________________________________________ >>> >>>>> aerogear-dev mailing list >>> >>>>> aerogear-dev(a)lists.jboss.org >>> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>>> >>> >>>> -- qmx >>> >>>> >>> >>>> >>> >>>> _______________________________________________ >>> >>>> aerogear-dev mailing list >>> >>>> aerogear-dev(a)lists.jboss.org >>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> aerogear-dev mailing list >>> >>> aerogear-dev(a)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(a)lists.jboss.org >>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> > >>> > >>> > _______________________________________________ >>> > aerogear-dev mailing list >>> > aerogear-dev(a)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(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >

looks nice in the webview, but I guess a bit too much text for something like: curl -v -H "Accept: application/json" -H "Content-type: application/json" -X GET http://controllerdemo-danbev.rhcloud.com/aerogear-controller-demo/delorean -M On Tue, Oct 9, 2012 at 10:52 AM, Daniel Bevenius <daniel.bevenius(a)gmail.com&gt; wrote: > I've added an example which you can find here (click on the delorean page to > see the general error page): > http://controllerdemo-danbev.rhcloud.com/aerogear-controller-demo/ > > I'll get in touch with the design folks at Red Hat but perhaps something > like this would make due until we have something proper in place. > > > On 8 October 2012 15:46, Daniel Bevenius <daniel.bevenius(a)gmail.com&gt; wrote: >> >> Created https://issues.jboss.org/browse/AEROGEAR-515 to track this issue. >> >> Thanks for all the comments! >> >> >> On 8 October 2012 15:37, Daniel Bevenius <daniel.bevenius(a)gmail.com&gt; >> wrote: >>> >>> Actually, qmx just informed me that this will not work at the moment. >>> I'll create a Jira for this so that this requirement is not lost though. >>> >>> >>> >>> On 8 October 2012 15:32, Daniel Bevenius <daniel.bevenius(a)gmail.com&gt; >>> wrote: >>>> >>>> You right, this is for any error. >>>> >>>> Let me look into this and try it out, and make sure that this works. >>>> >>>> Thx >>>> >>>> On 8 October 2012 15:30, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>> >>>>> On Mon, Oct 8, 2012 at 3:28 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: >>>>> > >>>>> > On Oct 8, 2012, at 8:26 AM, Matthias Wessendorf <matzew(a)apache.org > >>>>> > wrote: >>>>> > >>>>> >> On Mon, Oct 8, 2012 at 3:22 PM, Kris Borchers <kris(a)redhat.com&gt; >>>>> >> wrote: >>>>> >>> But that's what I'm saying. For example, say my app is trying to >>>>> >>> authenticate via a REST endpoint. I haven't specified an error page but auth >>>>> >>> fails and a 401 is returned. >>>>> >> >>>>> >> >>>>> >> >>>>> >> 401 != error >>>>> > >>>>> > But I thought this was for any error without a defined custom route, >>>>> > not just 500. Maybe I'm confused though. >>>>> >>>>> >>>>> correct - I am not awake :) >>>>> >>>>> >>>>> > >>>>> >> >>>>> >> 500 ==> error (+ stack trace) >>>>> >> >>>>> >> -M >>>>> >> >>>>> >> >>>>> >>> Since it's just a REST call, I don't want an error page but just >>>>> >>> some JSON back. I just want to make sure that is possible. >>>>> >>> >>>>> >>> On Oct 8, 2012, at 8:19 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>>>> >>> >>>>> >>>> I mean default error page, when the user doesn't specify one. >>>>> >>>> >>>>> >>>> On Oct 8, 2012, at 10:17 AM, Kris Borchers wrote: >>>>> >>>> >>>>> >>>>> I had the same thought but we should be careful. We don't want >>>>> >>>>> our error pages to be "too pretty" unless they can be customized based on >>>>> >>>>> the data type requested by the client. We have to keep mobile in mind and we >>>>> >>>>> don't want to be using a ton of data just to throw big fancy error pages at >>>>> >>>>> the app, especially if it's an AJAX request or data being sent over a >>>>> >>>>> websocket and it won't even be displayed. In that instance, less would be >>>>> >>>>> more. >>>>> >>>>> >>>>> >>>>> On Oct 8, 2012, at 8:13 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>>>> >>>>> >>>>> >>>>>> What about asking our design overlords (cough James Cobb cough) >>>>> >>>>>> about it? This is something that if we do right, will help a lot to improve >>>>> >>>>>> mindshare (beautiful error pages and consistent l&f). >>>>> >>>>>> >>>>> >>>>>> >>>>> >>>>>> On Oct 8, 2012, at 9:39 AM, Daniel Bevenius 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? >>>>> >>>>>>> 2. Should we have a button which can be used to display the >>>>> >>>>>>> stacktrace? >>>>> >>>>>>> >>>>> >>>>>>> Any suggestions are as always most welcome. >>>>> >>>>>>> >>>>> >>>>>>> Thanks, >>>>> >>>>>>> >>>>> >>>>>>> /Daniel >>>>> >>>>>>> <ErrorPage.png>_______________________________________________ >>>>> >>>>>>> aerogear-dev mailing list >>>>> >>>>>>> aerogear-dev(a)lists.jboss.org >>>>> >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>>> >>>>> >>>>>> -- qmx >>>>> >>>>>> >>>>> >>>>>> >>>>> >>>>>> _______________________________________________ >>>>> >>>>>> aerogear-dev mailing list >>>>> >>>>>> aerogear-dev(a)lists.jboss.org >>>>> >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> >>>>> aerogear-dev mailing list >>>>> >>>>> aerogear-dev(a)lists.jboss.org >>>>> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>>> >>>> -- qmx >>>>> >>>> >>>>> >>>> >>>>> >>>> _______________________________________________ >>>>> >>>> aerogear-dev mailing list >>>>> >>>> aerogear-dev(a)lists.jboss.org >>>>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>> >>>>> >>> >>>>> >>> _______________________________________________ >>>>> >>> aerogear-dev mailing list >>>>> >>> aerogear-dev(a)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(a)lists.jboss.org >>>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> > >>>>> > >>>>> > _______________________________________________ >>>>> > aerogear-dev mailing list >>>>> > aerogear-dev(a)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(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>> >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

What about asking our design overlords (cough James Cobb cough) about it?

What about asking our design overlords (cough James Cobb cough) about it? This is something that if we do right, will help a lot to improve mindshare (beautiful error pages and consistent l&f). On Oct 8, 2012, at 9:39 AM, Daniel Bevenius 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? > 2. Should we have a button which can be used to display the stacktrace? > > Any suggestions are as always most welcome. > > Thanks, > > /Daniel > <ErrorPage.png>_______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- qmx _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev