Page History

Overview

This provides some convenience methods to make it easier to do programmer level logging.

This provides information useful for debugging and error remediation by a programmer.

.

Design Goals

• It should support globalization so that the logs are in the language that the application developers/maintainers want to read
• It should facilitate the use of Error Numbers organized into a developer specified category structure "ACC-1024 - accounting error 1024" "MAN-1024 - manufacturing error 1024.
• Thread-safe.

Basic Architecture

Uses SLF4J to create log files.

Additional Loggig Functions

There is also a need for support for Audit Trails and User Error Logs.

Audit Trail support makes it easier for application developers to provide information about tasks completed and entities affected.

Error Logs provide non-technical managers with explanations of errors detected during operations that may or may not have any UI interaction.

These can be caused by batch process, interaction with external systems and any situation where the information required to fix a problem is beyond the scope of the end-user.

The Error Log can provide a plain language statement of the cause of the error. It is different from the programmer log as it is meant to be read by a person who knows the application area but not the structure of the program.

Configuration errors, gateway failures, bulk data errors and data integrity issues are examples of where the Error Log can help the administrator(s) of the application make the corrective actions or dispatch the problem to the appropriate tecnical people.