S
slacroixak
Guest
Thank you for your reply Fernando. There will be concerns for people that already use structured error handling and that educate existing AppSever invocations to go asynchronous, because at present the thrown error object gets lost (and nothing will appear in the AppServer log file). For now, the way I found to catch error details is to add a Progress.Lang.Error object extra output param (or as a property or in an extra serializable response object output param), prepared in a main catch of the called .p procedure. This topic is somehow connected to the unhandled exception idea we were mentioning with Laura this year. It would be nice to bring all that together (ability to catch details about stop conditions as well)
Continue reading...
Continue reading...