It might be worth overriding the code on server to catch any
exceptions and string-ify its stacktrace and throw back to client
some exception they both understand.
On 21/02/2008, at 7:13 AM, Pierce T. Wetter III wrote:
So I get this backtrace (see below).
So this is some sort of config problem, brought on somehow by the
fact that I've moved all the .jar cruft we had hanging out in /
Library/Java/Extensions into a framework. It looks like the server
is forwarding some sort of EOGeneralAdaptorException to the client
which might have had useful information in it but client has no
idea how to unarchive it because for some reason it can't access
eocasses, so it then throws a completely different exception on the
client side.
with regards,
--
Lachlan Deck
_______________________________________________
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]
