You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Dave Dombrosky <do...@gmail.com> on 2008/06/25 23:01:53 UTC
[T5] Return HTTP Error from AJAX Call
I would like to return an HTTP error from an AJAX call, so that it
will be interpreted as a failed request by my response handlers. Is
there any way to bypass Tapestry's ExceptionReport and instead have an
Exception bubble up to Tomcat (so that a 500 Error is generated)?
-Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [T5] Return HTTP Error from AJAX Call
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Em Wed, 25 Jun 2008 18:01:53 -0300, Dave Dombrosky <do...@gmail.com>
escreveu:
> I would like to return an HTTP error from an AJAX call, so that it
> will be interpreted as a failed request by my response handlers. Is
> there any way to bypass Tapestry's ExceptionReport and instead have an
> Exception bubble up to Tomcat (so that a 500 Error is generated)?
In addition, how could I bypass an AJAX request and force a traditional
request? I tried to simply return null or "this" in the event handler
method, but it is handled as an AJAX request.
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [T5] Return HTTP Error from AJAX Call
Posted by "Filip S. Adamsen" <fs...@fsadev.com>.
Maybe this will help, it's a HttpStatusCode class and a
ComponentEventResultProcessor that handles it:
http://www.mail-archive.com/users@tapestry.apache.org/msg23885.html
-Filip
On 2008-06-25 23:01, Dave Dombrosky wrote:
> I would like to return an HTTP error from an AJAX call, so that it
> will be interpreted as a failed request by my response handlers. Is
> there any way to bypass Tapestry's ExceptionReport and instead have an
> Exception bubble up to Tomcat (so that a 500 Error is generated)?
>
> -Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org