feature request #8706
taxeditor error report with timestamps
100%
Description
Wie wäre es wenn wir dem Fehlerprotokoll mal einen Timestamp spendierten? Damit wäre es leichter den Fehler einem bestimmten Server Problem oder Zustand zuzuordnen.
Ich schlage zwei timestamps vor:
- local date time
- last server response date time
Die "last server response date time" sollte relativ einfach aus der HTTPInvoker Komponente zu bekommen sein. So wie überall in Spring, müsste es auch hier möglich sein, sich mit einem eigenen Bean hier einzuklinken, um dann denn "Date" HTTP-Header jeder Serverantwort in eine "Session-Variable" von Eclipse oder Spring zu speichern.
Beispiel für einen HTTP-Date-Header:
Date: Tue, 19 Nov 2019 07:16:35 GMT
Associated revisions
ref #8706 reporting error time in messages
ref #8706 DateHeaderFilter to add Date headers to all servelet responses
fix #8706 error messages with remonte request time stamps
ref #8706 DateHeaderFilter to add Date headers to all servlet responses
ref #8706 moving DateHeaderFilter to cdmlib-remote to make it available for cdm-vaadin
ref #8706 adapting to new DateHeaderFilter package name
History
#1 Updated by Andreas Kohlbecker over 1 year ago
- Status changed from New to In Progress
- Assignee changed from Katja Luther to Andreas Kohlbecker
- Target version changed from Unassigned CDM tickets to Release 5.12
#2 Updated by Andreas Kohlbecker over 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 50
Applied in changeset taxeditor|6e1d17962e4f23d254da242b13a7e188d69793ca.
#3 Updated by Andreas Kohlbecker over 1 year ago
- Assignee changed from Andreas Kohlbecker to Andreas Müller
ready for review
#4 Updated by Andreas Müller 6 days ago
- Status changed from Resolved to Closed
- % Done changed from 50 to 100
I guess we can close this ticket. Timestamping generally works. Open new ticket if there are open issues left.
