Recent serialization changes have broken UserSetting and SystemSetting services.
These services were taking in the content-type “text/plain” until now, basically a json with key / value pairs of settings.
I think the RenderServiceMessageConverter now lets in only json or xml payload. This is the cause of the bug.
We could change the UserSetting and SystemSetting services to take in json content type. But there is one more issue.
RenderServiceMessageConverter tries to de-serialize the json input into an object, for these said services an object is unnecessary since what is persisted/ later accessed in dhis is just a json.
Recent serialization changes have broken UserSetting and SystemSetting services.
These services were taking in the content-type “text/plain” until now, basically a json with key / value pairs of settings.
I think the RenderServiceMessageConverter now lets in only json or xml payload. This is the cause of the bug.
We could change the UserSetting and SystemSetting services to take in json content type. But there is one more issue.
RenderServiceMessageConverter tries to de-serialize the json input into an object, for these said services an object is unnecessary since what is persisted/ later accessed in dhis is just a json.