Is it possible to enhance the error handling of servoyException to also give us the trace of the error? Currently, I get something like
Cannot convert null to an object
Great. But where did that happen?
Thanks
Patrick
Is it possible to enhance the error handling of servoyException to also give us the trace of the error? Currently, I get something like
Cannot convert null to an object
Great. But where did that happen?
Thanks
Patrick
I second this request. I’d like to be able to report in my own log file the method-stack and line number that provoked the error.
I seem to be getting the callstack now (wasn’t a moment ago) but still no line number. That would be nice.