I am importing the log4j file that I've attached to issue:
and am getting an exception being shown (with the loading being ended). In one way thats OK because it means the error handling is working now.
But I don't think we should do like it like that - in this particular case - since I did not setup the file - it was actually written like this by log4net. I attach the config file from Edi so you could generate the same format if you download and execute Edi
with this config file.
I propose to log a warning instead of throwing an exception for those cases that can be circumvented (like this one). The collection of warnings should be shown to the user whenever processing steps like load, save, export, load analysis session are finished
with non-zero entries.
My problem at this point is that I cannot test without having to edit the code (I have to uncomment the line number line that was reported in the other issue). So, please fix to enable us to continue testing with same conditions.