D
dbeavon
Guest
>> It has no idea that this error will be sent back to the client. I guess I was just agreeing with you that it would be considered a bug if an error (LockConflict for example) is both *thrown* to the clients/callers *and* it is written to the agent log at the same time. It seems redundant to do both. No mind-reading required. If a client/caller has caught the error, then it is their right to swallow it without logging it (either while still on the ABL side, or on the .Net openclient side). >> And in fact it is NOT going back to the client. Once the error message is written to the output device, the error message is gone. The message details may be gone, but the stop condition itself has always able to be sent back to the openclient as Progress.Open4GL.Exceptions.RunTime4GLStopException. As you say, there is very little detail in that exception to make sense of it. It is basically just another generic "something went wrong" exception. But if I catch a LockConflict and re-throw that as an AppError then I have captured all the underlying details I need. There is no annoying noise needed in the log (or I can put it there myself if I really want that) .
Continue reading...
Continue reading...