[SLING-3249] Cache not properly used in JcrPropertyMap

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JCR Resource 2.2.8
• Fix Version/s: JCR Resource 2.3.0
• Component/s: JCR
• Labels: perfomance
• Assignee: Carsten Ziegeler
• Reporter: Przemyslaw Pakulski
• Created: 18/Nov/13 12:14
• Updated: 17/Feb/14 15:48
• Resolved: 03/Jan/14 07:30

Description

JcrPropertyMap class has internal cache for properties an values.
The cache is not used correctly, e.g. reading the same property twice still results in access to underlying node.

The problem is with get() methods, when property is red it is put into the cache, but the cache is never checked if it already contains the property.
The only way to force the caching is to use readFully() method indirectly, in this case read method is examining the cache.

It looks this has been introduced by fixing SLING-2425.

Issue Links

• is broken by: SLING-2425 Incorrect and inconsistent escaping of property names used in JcrPropertyMap