When a resultcode is returned, the log level is always INFO. IMO, resultcodes (custom or native) always imply an error and should be logged by the framework as such.
Before being called resultcode, the name was errorcode. The log level being info is (as far as I can remember) a common decision with Operation. resultcode like invalid password, failed login are normal for the application and Operation should not be warned by these.
That why there are 2 types of resultcode: functional and technical.
The default is functional (logged at INFO)
You can change it by <resultcode name="..." type"technical">...</resultcode>
Then the CAPI will log the received error at WARN and/or ERROR level.
[TODO for me: check that it's described in the documentation]
Hope that answer your request.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Before being called resultcode, the name was errorcode. The log level being info is (as far as I can remember) a common decision with Operation. resultcode like invalid password, failed login are normal for the application and Operation should not be warned by these.
That why there are 2 types of resultcode: functional and technical.
The default is functional (logged at INFO)
You can change it by <resultcode name="..." type"technical">...</resultcode>
Then the CAPI will log the received error at WARN and/or ERROR level.
[TODO for me: check that it's described in the documentation]
Hope that answer your request.
It does for the custom resultcodes, thanks. However, is there some way to enforce this for the native codes?
I think that's correct for _InternalError and _InvalidResponse, for the others I don't think so.