Hi all,
I am currently using an EODistributionChannel.Delegate to handle request tracking. And am observing some weird behavior, so I am wondering if anyone else has experience with this...
1. If I set a custom delegate on the distribution channel, the JC runtime no longer catches the session expiration exception, so instead of getting a "Your session expired, etc." dialog, the exception propagates all the way and crashes my app. At first that made me think that there was a default delegate of sorts that I replaced, and therefore lost this functionality, but there is no default delegate... Any thoughts on this?
2. Not really about the delegate, but related... When a session expires, and I do get a dialog on the client side telling me it expired, it seems that the thread the request was made on (namely the Swing EDT) continues the execution even though a modal dialog is up. This is very bizarre. And it also causes additional exceptions to be thrown, resulting in my custom exception handler kicking in, and the GUI becoming a mess... Any thoughts on this?
3. I am wondering if I should ditch WO's default behavior, and simply implement a Delegate that will also deal with session expiration exceptions. However, the error state handling mechanism is not all what it could be, meaning: the only way I see of detecting if an exception occurred because of session expiration is to parse the exception's info text, which I am always reluctant to do, if there is another way. Any thoughts on this?
Fervently hoping to get some reply on this, F _______________________________________________ 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]
