Pawn2:Logging: Difference between revisions
From Adapt
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 7: | Line 7: | ||
* error - all unexpected error messages | * error - all unexpected error messages | ||
* trace - call trace | * trace - call trace | ||
** trace - call entry, exit, details of method parameters | ** trace - timing information | ||
** debug - call entry, exit, details of method parameters | |||
** info - overview of call and short description of parameters | ** info - overview of call and short description of parameters | ||
** error - any exceptions | ** error - any exceptions | ||
* process - logger for all 3rd processes | * process - logger for all 3rd processes | ||
* storage - logger for storage resources | * storage - logger for storage resources | ||
The two mapped diagnostic contexts are used: | |||
* session - current user session of call, or 3rd party process if not running in-line | |||
* wscall - current gwt call. may be set by items that will NEVER be called by a client | |||
Latest revision as of 19:05, 4 March 2009
Description of logging environment in PAWN 2.
Log4j is used for all logging in PAWN. GWT may log some things using the servlet logger, but all attempt has been made to redirect these back to one of the pawn loggers.
The following loggers are used withing pawn, guidelines on what to log to each level is also listed
- error - all unexpected error messages
- trace - call trace
- trace - timing information
- debug - call entry, exit, details of method parameters
- info - overview of call and short description of parameters
- error - any exceptions
- process - logger for all 3rd processes
- storage - logger for storage resources
The two mapped diagnostic contexts are used:
- session - current user session of call, or 3rd party process if not running in-line
- wscall - current gwt call. may be set by items that will NEVER be called by a client
