Raising exceptions

Data Abstract
1

Hi,

Just wanted to raise this topic as I think it could be improved. I stumbled upon various exceptions of the same type being raised for for different issues. This is OK, but how to differentiate these on the client gets cumbersome when I am checking for existence of certain text in a RO raised exception message.

For instance EROSuperChannelException, can be raised for any number of issues. ‘Package too Large’, TimeOuts, ‘No thread pool assigned’, ‘Unknown response…’. I find my self adding in new exception handling as we stumble across errors - package too large for found with uploading images as an example.

Instead of just using text, can we assign an exception specifically, or add error numbers?

Is there a list of every raised message, and what a possible resolution is?

Does any one have any ideas on this for improvement or are you happy with the way it is?

I guess this is for SDK as well!

2

Hello,

This makes sense, yes. We are planning the similar thing:
45851: Improve exceptions hierarchy in RO
i.e. we plan to provide exception classes hierarchy so the exceptions processing (including the message customization or localization) can be based on the exception class. Unfortunately I cannot promise any concrete timing for this.

Best regards - Sergey.