You right, this is for any error.<div><br></div><div>Let me look into this and try it out, and make sure that this works. </div><div><br></div><div>Thx</div><br><div class="gmail_quote">On 8 October 2012 15:30, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Mon, Oct 8, 2012 at 3:28 PM, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a>> wrote:<br>
><br>
> On Oct 8, 2012, at 8:26 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
><br>
>> On Mon, Oct 8, 2012 at 3:22 PM, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a>> wrote:<br>
>>> 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.<br>
>><br>
>><br>
>><br>
>> 401 != error<br>
><br>
> But I thought this was for any error without a defined custom route, not just 500. Maybe I'm confused though.<br>
<br>
<br>
</div>correct - I am not awake :)<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
><br>
>><br>
>> 500 ==> error (+ stack trace)<br>
>><br>
>> -M<br>
>><br>
>><br>
>>> 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.<br>
>>><br>
>>> On Oct 8, 2012, at 8:19 AM, Douglas Campos <<a href="mailto:qmx@qmx.me">qmx@qmx.me</a>> wrote:<br>
>>><br>
>>>> I mean default error page, when the user doesn't specify one.<br>
>>>><br>
>>>> On Oct 8, 2012, at 10:17 AM, Kris Borchers wrote:<br>
>>>><br>
>>>>> 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.<br>
>>>>><br>
>>>>> On Oct 8, 2012, at 8:13 AM, Douglas Campos <<a href="mailto:qmx@qmx.me">qmx@qmx.me</a>> wrote:<br>
>>>>><br>
>>>>>> 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).<br>
>>>>>><br>
>>>>>><br>
>>>>>> On Oct 8, 2012, at 9:39 AM, Daniel Bevenius wrote:<br>
>>>>>><br>
>>>>>>> Hi all,<br>
>>>>>>><br>
>>>>>>> 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.<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>
>>>>>>> 2. Should we have a button which can be used to display the stacktrace?<br>
>>>>>>><br>
>>>>>>> Any suggestions are as always most welcome.<br>
>>>>>>><br>
>>>>>>> Thanks,<br>
>>>>>>><br>
>>>>>>> /Daniel<br>
>>>>>>> <ErrorPage.png>_______________________________________________<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>
>>>>>> -- qmx<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>
>>>>><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>
>>>> -- qmx<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>
>>><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>
>> 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>
>> _______________________________________________<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>
<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>
_______________________________________________<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>