Note for the update guide:
If you are using a custom Exception Page, make sure you check out the
changes made to the default exception page. In particular, your exception
page won't render correctly after an XHR request unless it renders with an
empty or null DOCTYPE.
Jeremy
Jeremy F. Kassis
OK. I think I've got this mostly figured out.
As it turned out, I had already configured the exceptionPageName using the
tapestry.InfrastructureOverrides configuration point. When I was on Tap
4.0.2, it looked like this:
Also in Tap 4.0.2, I had done some funk
Hi Jessek!
This sounds right on.
Since a few service points, including DojoAjaxResponseBuilder get the
exceptionPageName from the Infrastructure service point, I tried to add a
contribution to the Infrastructure service point configuration as follows:
But Hivemind doesn't seem to
The DojoAjaxResponseBuilder handler currently gets configured with the
names of pages representing exceptions in order to detect an exception
page and properly render the response so it is presented properly for
ajax requests.
This configuration currently is done via hivemind :
http://tapestry.a
I just noticed something that seems related. The browser reports a syntax
error in dojo/src/browser_debug.js:
missing } after function body
browser_debug.js (line 17)
document.write("dojo.hostenv._global_omit_module_check =
false;");dojo.hostenv._l
