[MAGNOLIA-2746] Content api is inconsistent with regards to exception handling Created: 25/May/09  Updated: 19/Jan/10  Resolved: 19/Jan/10

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Critical
Reporter: Magnolia International Assignee: Philipp Bärfuss
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MAGNOLIA-3018 content API cleanup: Content.getNodeD... 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)

 Description   

Just one example amongst others:
info.magnolia.cms.core.DefaultContent#getNodeData - ignores and swallows RepositoryException.
info.magnolia.cms.core.DefaultContent#hasNodeData - does not.


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