[MAGNOLIA-4122] rendering: ExceptionHandling should not only react on RenderException Created: 01/Feb/12  Updated: 02/Aug/16  Resolved: 02/Aug/16

Status: Closed
Project: Magnolia
Component/s: rendering
Affects Version/s: 4.5.1
Fix Version/s: 4.5.x

Type: Improvement Priority: Neutral
Reporter: Daniel Lipp Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-4339 rendering: improve exception handling Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Right now rendering ExceptionHandling just catches RenderException's and basically just logs the stack trace. In order to get better hints to the source of problems we should treat all Throwables. As non-RenderException's may not contain important infos's as e.g. the template name we'll have to extract these from the RenderingContext in order to simplify tracing errors.



 Comments   
Comment by Michael Mühlebach [ 02/Aug/16 ]

Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
Given that the this issue has seen no attention for quite a while and belongs to an old version, we're not going to address this issue any more. Instead we will focus on issues with a higher impact and more votes.
Under the assumption this issue is no longer relevant, I'm going to close it to set expectations so the issue doesn't stay open for ages with no updates. If it is still relevant please feel free to open a new issue in the appropriate project.

Generated at Mon Feb 12 03:52:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.