The Cúram infrastructure produces trace records in specific categories with specific levels. This allows them to be easily filtered in a log4j viewer. The categories and levels supported are described in the following table where <BPO>, <Entity> and <Facade> are the names of the relevant Cúram class. The <CodePackage> field is left empty if the class is not located in a code package.
Category |
Level |
Meaning |
|---|---|---|
Trace |
Error |
Loggable exceptions which have not been caught in the code. |
Trace.BatchLauncher |
Info |
Progress of Batch Launcher |
Trace.BatchLauncher |
Error |
Errors in Batch Launcher |
Trace.CodeTable |
Debug |
Tracing information about code table lookups. |
Trace.DataAccess.<Entity> |
Info |
SQL statements executed by entity objects. |
Trace.DataAccess.<Entity> |
Debug |
Results of SQL select statements. |
Trace.Methods.<CodePackage>.<BPO> |
Info |
Business Object method invocation. |
Trace.Methods.<CodePackage>.<BPO> |
Debug |
Arguments and types of arguments for Business Object method invocation. |
Trace.Rules |
Info |
Progress of Rules Engine. |
Trace.ServerCalls.<CodePackage>.<Facade> |
Info |
Server method invocations by remote clients. |
Trace.ServerCalls.<CodePackage>.<Facade> |
Debug |
Arguments and types of arguments for server method invocation. |
Trace.Tools |
Info |
Progress of build time tools. E.g: configtest |
Trace.Tools |
Warning |
Warnings from build time tools |
Trace.Tools |
Error |
Errors from build time tools |