Hi!
Suppose I want to throw a chained exception over the wire. The cause of the exception is a class that might not be present on the client receiving the exception. What can I do?
1) The obvious: no chaining. Copy the message from the underlying exception into a brand new one, and loose the stacktrace (or at least log it to the serverlog).
2) Maybe I can copy the exception details from the old exception into the new one? It's just textual data, right?
Can somebody please give advice on what the usual approach is in such situations? Thanks a lot!
Regards,
Michael
Suppose I want to throw a chained exception over the wire. The cause of the exception is a class that might not be present on the client receiving the exception. What can I do?
1) The obvious: no chaining. Copy the message from the underlying exception into a brand new one, and loose the stacktrace (or at least log it to the serverlog).
2) Maybe I can copy the exception details from the old exception into the new one? It's just textual data, right?
Can somebody please give advice on what the usual approach is in such situations? Thanks a lot!
Regards,
Michael