Mapping client-side TeamRepositoryException error codes
When code from the client side invokes a server side code, the error messages thrown in the Server Side do NOT map to those thrown on the client side (REST interfaces, probably no way to map).
However, the generic message on the client side TeamRepositoryException does start with a code, that *seems* like it could be mapped to a more user-explainable error. For the server side error that includes "duplicate key value in a unique or primary key constraint", I get on the client side "CRJAZ0098I The service ... server returned the http error 500 with error text "Internal Server Error"".
I think that the code CRJAZ0098I could be used to map to the actual cause. Does anyone have any information on this?
However, the generic message on the client side TeamRepositoryException does start with a code, that *seems* like it could be mapped to a more user-explainable error. For the server side error that includes "duplicate key value in a unique or primary key constraint", I get on the client side "CRJAZ0098I The service ... server returned the http error 500 with error text "Internal Server Error"".
I think that the code CRJAZ0098I could be used to map to the actual cause. Does anyone have any information on this?