![]() ![]() So what are the actual problems and why do we need to do something about it? Why the Current Situation Is Not Ideal? This is one of the problems, but also it can become messy and very hard to maintain and debug problems when we encounter error edge cases. Keeping track of Exceptions and being able to follow the code becomes more difficult. Unless you know of that specific class, you won’t find where the logic is being applied by just following the normal flow of the code. This is the case of Spring’s exception handlers for example. In these recent few decades where we have seen a boom in the programming sector, it became a widespread habit to bubble up exceptions in our code and then do the exception handling at some hidden point in our code, a place very difficult to find for any developer that didn’t know the code well in most of the cases. In this article we’re going to go through one of the most common problems in exception handling in any JVM-language and what alternative can we use to achieve a clearer, cleaner and more maintainable code in terms of error handling.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |