Maybe I've screwed up the exception page handling somehow ....Currently the ajax response handler looks specifically for exception pages matching any of the configurable exception page names via:
http://tapestry.apache.org/tapestry4.1/developmentguide/exceptionpages.html Are you somehow using different names ? If you have more specifics about how you are contributing your custom exception page and possibly add it and the issue to JIRA I can look in to it. The infrastructure is in place and works well when the default exception pages are rendered for notifying the client in a friendly "ajax way" when exceptions happen. (as in something similar to http://opencomponentry.com:8080/tacos/ajax/ExceptionHandlerExample.html ) On 6/27/07, Malin Ljungh <[EMAIL PROTECTED]> wrote:
Hi, I'm trying to "ajaxify" my app and I have problem with my custom exception page. If an unexcpected exception occurs my custom exception is executed. Problem is that the client sees nothing of this (of course) since the ID I've specified in the updateComponents does not exist in my custom exception page. I can see that the exception page is delivered in Firebug but nothing is (of course) displayed to the user. (All I can get is a debug message like 'WARNING: 10:52:20: No ajax-response elements recieved.') How should this be handled? I've read that it should work at least if I don't use a custom exception page, but I've not tried this since I'd like a little friendlier message to my users. Cheers, Malin
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
