Just saw how bug35 was fixed, and wanted to note that someone might run into problems even now.
Tapestry AbstractEngine handles PageRedirectException a bit differently. It checks to see if a second PageRedirectException is thrown while activating the new page (for instance in the page validate method) and then activates that second page - until no PageRedirectExceptions occur. So, it is possible that we can end up in the page we started. Tacos implementation will also end up (through a javascript redirect) to the same page but there will be a slight difference. State (private page fields mostly) will have been lost. So, it is probable that in the near future we will get another bug report on this, saying that he is seeing different things when moving from @Form to @AjaxForm. BTW, i actually thought that this would be resolved by doing exactly what Tapestry does and then returning a special ajax response code along with the complete html page. Then tacos.js would replace the whole page instead of the given portion. But ofcourse, thats easier said than done :) ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Tacos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tacos-devel
