[MAGNOLIA-4764] RenderingFilter#getNodedataAsStream unnecessarily relies on Exceptions for execution flow Created: 08/Jan/13  Updated: 11/Feb/13  Resolved: 10/Jan/13

Status: Closed
Project: Magnolia
Component/s: rendering
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Bug Priority: Trivial
Reporter: Daniel Lipp Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLSTK-1065 Flash content is not rendered 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

In getNodedataAsStream (line 257) we try to read the property JcrConstants.JCR_DATA even if we know it's not around (line 250). The resulting PathNotFoundException could easily be avoided.



 Comments   
Comment by Daniel Lipp [ 08/Jan/13 ]

The problem was discovered because of MGNLSTK-1065.

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