Re: Tapestry 4.1.1 async and RedirectException

2007-02-08 Thread Jesse Kuhnert
Ehh...No not really. I mean it is sort of, which is what it should be doing. Of course I don't have a remote debugger hooked up to your machine so I can't decipher what isn't working for you. On 2/8/07, Daniel Tabuenca <[EMAIL PROTECTED]> wrote: Well... didn't work for me. I got the new page as

Re: Tapestry 4.1.1 async and RedirectException

2007-02-08 Thread Daniel Tabuenca
Well... didn't work for me. I got the new page as part of the response but it didn't render anywhere (just saw it in firebug). Is it possible to send some sort of javascript to actually redirect the browser to a new page? That is I don't want to send the new content and replace the old one wit

Re: Tapestry 4.1.1 async and RedirectException

2007-02-08 Thread Jesse Kuhnert
It works...But not in the same way tacos does it and it's "not reccomended". I only added it in there so that people wouldn't get tripped up when it happened. (myself included ;) ) If it works then consider yourself lucky. (it does work of course, but it's questionable how well the page you get

Tapestry 4.1.1 async and RedirectException

2007-02-08 Thread Daniel Tabuenca
Does Tapestry 4.1.1 handle RedirectExceptions in ajax responses? I remember Tacos intercepted them and generate javascript in the response to do the actual re-direction. Is this implemented in Tapestry? How do I do this? - To uns