[MAGNOLIA-4539] HTMLEscapingPropertyWrapper and possibly other wrappers do not conform to the JCR API. Created: 19/Sep/12  Updated: 01/Oct/12  Resolved: 27/Sep/12

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

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

Node.getProperty('x') should throw a PathNotFoundException if the x property doesn't exist - according to javadoc. In Magnolia, I get an instance of HTMLEscapingPropertyWrapper, which ends up blowing an NPE when i try to getString(). Not the expected behavior.

I wasn't able to trace back where the null comes from in the first place, but it kinda sounds like there might be other side-effects/misinterpretation of the api with our wrappers, etc. Please investigate and ensure proper and consistent behavior.


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