Opened 20 months ago
Last modified 20 months ago
#2867 assigned defect
Try to better explain why a localized exception message could not be retrieved
Reported by: | jng | Owned by: | jng |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | General | Version: | |
Severity: | trivial | Keywords: | |
Cc: | External ID: |
Description
Sometimes a localized exception message fails to be retrieved because due to an internal coding error, an exception was thrown with no or insufficient arguments to properly format the required exception message.
This error is currently discarded and the generic "failed to retrieve message" message is returned instead.
Where possible we should try to capture the source error and include this as the reason for the "failed to retrieve message". This will at least give internal developers a clue to where an exception is thrown without the required message arguments.
Change History (2)
comment:1 by , 20 months ago
Milestone: | 4.0 |
---|
comment:2 by , 20 months ago
Summary: | Better try to explain why a localized exception message could not be retrieved → Try to better explain why a localized exception message could not be retrieved |
---|
This is actually harder than initially thought due to the exception message formatting code being in
MgException
itself and the formatting code potentially throwingMgException
s itself and how to avoid a super-recursively nested explanation error message as a result.Milestone removed.