Hi Andrey,
Vicente Botet wrote:
Reading the code I see a lot of
try{ // } catch (...){ // Something has gone wrong. }
Does it mean that the application is unable to know when things go wrong?
Yes. Although extremely useful, logging is an auxiliary feature of the application, so it must not influence business logic.
this statement is not true for the general case. Logging *may* be an auxiliary feature, i.e. when thinking about debug output that's of interest mostly for software developers, but there are applications that must leave a reliable audit trail, i.e. systems that deal with money and finances. For those applications, logging is part of the business logic. The same is true to some extend for applications that run in the background, like network servers, etc.
That is, users should not be bothered to wrap every log statement in a try/catch block.
However, users that do want to deal with those exceptions themselves should be able to. Take care, Peter