THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Implementation of the LogSubject
Each of these _MessageStatusLogger_s will be repsonsible for the correct formatting of the the Logging Entity detail LogSubjects will ensure they toString according to the format design.
...
The following classes will have logging added to provide the required log messages specified in the Functional Specification. To be able to correctly log the Actor involved with the log statement a number of supporting classes will need to be modified so that the Actor can be passed through to the class listed here.
Main
| No Format |
|---|
BRK-1001 : Startup : Version: <Version> Build: <Build> BRK-1004 : Ready BRK-1007 : Using logging configuration : <path> |
...
| No Format |
|---|
_logger.info("Binding queue:" + queue + " with routing key '" + routingKey + "' to exchange:" + this);
_logger.debug("Loading configuration for virtualhost: " + config.getName());
|
Feedback
ID | From | Comment | Response |
|---|---|---|---|
1 | Marnie | Ensure data logged in messaged due to be deleted is not lost. |
|
2 | Marnie | Following 1: Exception handling messages need further thought as replacing with 'Close' messages loses the cause |
|
3 | Marnie | Be mindful of performance in generating these log messages |
|
4 | Marnie | It is not clear that the LogActors, LogSubjects will be created and attached to their repective model objects |
|