First consideration for any Application Programming Interface (API) is how it will evolve in the future. This critical interface must stand the test of time, and should whenever possible be both upgrade and downgrade compatible. Continue reading
This is a usability problem that I have run into a number of times. A programmer writes a UI screen to receive a long list of inputs in order to create an object in system. Save is enabled only when all the inputs are filled in and verified valid. This is a big problem. Continue reading
This general design principle does not mean to never change anything, but to consciously create a paradigm where the same things have the same names and are accessed in the same way as much as possible. Continue reading
When you make a web service call, you want to report the problem to the user save as you do for any other part of the program, and that is through an exception object. This post talks about converting the JSON received back into an exception object so that it can be reported properly. This is the fourth post in a series about translatable errors for REST web services. Continue reading
We need to construct an object which has a template and a set of parameter data values. Java offers a couple of ways to do this, and this post shows how the variable parameter mechanism works easily and conveniently for this purpose. Continue reading
Second in a series on translatable exceptions, this discusses how an error message should be returned as JSON from a web-service API so that it the calling program can display the error in the right language for the user. Continue reading
This is the first of a series of posts, I want to go over some of the groundwork of what it takes to make exceptions localizable into other languages. Nothing new here, but just want to explain clearly the requirements of a localizable exception messages.