On 27/01/2009, at 5:11 PM, Chuck Hill wrote:
FireBug and FireFox. Take a look at the Net log. You can see all the traffic back and forth. Often these things came in an Ajax update and so don't show up in the page source (as originally loaded).
This might be a good time to mention that the Exception is being thrown in an action method called by an AjaxUpdateLink. (I put it there because that guarantees the error-page-inside-AUC phenomenon which I'm trying to stop.) I note Mike's comment in another thread:
it sounded like you had an AjaxUpdateLink that returned a new component? It didn't work because "it doesn't work that way". Ajax updates are just changing state on a single page, not transitioning between pages. You put the page in an inconsistent state by returning a new component from your update.
Is that the issue here? Or should AjaxUtils.redirectTo() avoid this in my case?
-- Paul. w http://logicsquad.net/ h http://paul.hoadley.name/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
