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). Look at the response content in FireBug and you should be
able to find it.
Sorry Chuck, I'm obviously having a slow afternoon (and it's 41ºC
here)
It is snowing here. I am willing to trade.
---I assume you mean to look using the Net log on the page where I'm
generating the Exception, but _after_ the exception has been thrown,
right? I don't get the chance, as the app responds to the request,
returning the login page, and the inspector is updated. Am I
looking in the right place?
Yes, almost. What I would do is go to this before you trigger the
exception and hit Clear. Then trigger the exception, and see what
show up. Then expand the notes that are for things like 0.3.4.5
(ignore the requests for .css and .js file), and click on the Response
tab. The contents of the Response tab are what the server returned
for that request. There will likely be more than one to look through.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
