[MAGNOLIA-6817] Make LockException error messages more human-readable Created: 12/Oct/16  Updated: 12/Oct/16

Status: Accepted
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Cedric Reichenbach Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot from 2016-10-12 14-24-32.png    
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   

Currently, the `LockException` is bubbled all the way up and rendered into a not-so-insightful error message in the UI (see Screenshot from 2016-10-12 14-24-32.png), especially for non-technical users.

Instead, that exception should either be caught and wrapped or prevented in order to at least throw a more well-formulated one. Something like "Node to be restored was locked by another operation - try again later" would make much more sense to end users.


Generated at Mon Feb 12 04:18:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.