NSForwardException and InvocationTargetException?
NSForwardException and InvocationTargetException?
- Subject: NSForwardException and InvocationTargetException?
- From: Jonathan Rochkind <email@hidden>
- Date: Wed, 26 Mar 2003 14:25:44 -0600
Can anyone explain the weird relationship between InvocationTargetException
and NSForwardException?
If, just for testing purposes, I actually manually throw an
InvocationTargetException in my code... in Applicaiton.handleException(),
the exception I get passed in as an argument is actually an
NSForwardException----who's originalException() is NOT an
InvocationTargetException, but rather is the original
InvocationTargetException's getTargetException(). If you're following, the
InvocationTargetException has been magically transformed to a similar
NSForwardException. Which has had it's stack trace filled in to the same
line as the original InvocationTargetException, to make matters more
confusing.
But, I am currently logging all exceptions that make it up to the
Application.handleException. And I DO have InvocationTargetExceptions in
the log. So sometimes InvocationTargetException IS passed in to
handleException. To make matters more mysterious, when I look at the
stackTrace of that logged InvocationTargetException---it's coming from a
line where I have no idea how that line could have generated an
InvocationTargetException. I expect it generated some other exception, and
WO chose to wrap it in an InvocationTargetException (instead of in an
NSForwardException?!?!)
So, I'm not even sure what it is I'm asking. But there's something wacky
going on with WO and InvocationTargetException and NSForwardException. Can
anyone explain all this stuff? Is there useful documentation somewhere?
--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.