Yeah, you are right, this should be taken care of once we complete:<div><a href="https://issues.jboss.org/browse/AEROGEAR-515">https://issues.jboss.org/browse/AEROGEAR-515</a></div><div><br></div><div><br><div class="gmail_quote">
On 9 October 2012 11:04, 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">
looks nice in the webview, but I guess a bit too much text for something like:<br>
<br>
curl -v -H "Accept: application/json" -H "Content-type:<br>
application/json" -X GET<br>
<a href="http://controllerdemo-danbev.rhcloud.com/aerogear-controller-demo/delorean" target="_blank">http://controllerdemo-danbev.rhcloud.com/aerogear-controller-demo/delorean</a><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
-M<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Tue, Oct 9, 2012 at 10:52 AM, Daniel Bevenius<br>
<<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:<br>
> I've added an example which you can find here (click on the delorean page to<br>
> see the general error page):<br>
> <a href="http://controllerdemo-danbev.rhcloud.com/aerogear-controller-demo/" target="_blank">http://controllerdemo-danbev.rhcloud.com/aerogear-controller-demo/</a><br>
><br>
> I'll get in touch with the design folks at Red Hat but perhaps something<br>
> like this would make due until we have something proper in place.<br>
><br>
><br>
> On 8 October 2012 15:46, Daniel Bevenius <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:<br>
>><br>
>> Created <a href="https://issues.jboss.org/browse/AEROGEAR-515" target="_blank">https://issues.jboss.org/browse/AEROGEAR-515</a> to track this issue.<br>
>><br>
>> Thanks for all the comments!<br>
>><br>
>><br>
>> On 8 October 2012 15:37, Daniel Bevenius <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> Actually, qmx just informed me that this will not work at the moment.<br>
>>> I'll create a Jira for this so that this requirement is not lost though.<br>
>>><br>
>>><br>
>>><br>
>>> On 8 October 2012 15:32, Daniel Bevenius <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> You right, this is for any error.<br>
>>>><br>
>>>> Let me look into this and try it out, and make sure that this works.<br>
>>>><br>
>>>> Thx<br>
>>>><br>
>>>> On 8 October 2012 15:30, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>>><br>
>>>>> 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>><br>
>>>>> > wrote:<br>
>>>>> ><br>
>>>>> >> On Mon, Oct 8, 2012 at 3:22 PM, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a>><br>
>>>>> >> wrote:<br>
>>>>> >>> But that's what I'm saying. For example, say my app is trying to<br>
>>>>> >>> authenticate via a REST endpoint. I haven't specified an error page but auth<br>
>>>>> >>> 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,<br>
>>>>> > not just 500. Maybe I'm confused though.<br>
>>>>><br>
>>>>><br>
>>>>> correct - I am not awake :)<br>
>>>>><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<br>
>>>>> >>> 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<br>
>>>>> >>>>> our error pages to be "too pretty" unless they can be customized based on<br>
>>>>> >>>>> the data type requested by the client. We have to keep mobile in mind and we<br>
>>>>> >>>>> don't want to be using a ton of data just to throw big fancy error pages at<br>
>>>>> >>>>> the app, especially if it's an AJAX request or data being sent over a<br>
>>>>> >>>>> websocket and it won't even be displayed. In that instance, less would be<br>
>>>>> >>>>> 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)<br>
>>>>> >>>>>> about it? This is something that if we do right, will help a lot to improve<br>
>>>>> >>>>>> 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<br>
>>>>> >>>>>>> default error page in aerogear-controller. This is the page that a user will<br>
>>>>> >>>>>>> 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<br>
>>>>> >>>>>>> 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<br>
>>>>> >>>>>>> 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>
>>>><br>
>>>><br>
>>><br>
>><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>
--<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>
</div></div></blockquote></div><br></div>