[SLING-8943] The Sling API ObjectConverter does not correctly convert JCR values

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: API 2.21.0
• Fix Version/s: API 2.22.0
• Component/s: API
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 20/Dec/19 13:42
• Updated: 15/Jan/20 15:43
• Resolved: 06/Jan/20 09:11

Description

SLING-8116 delegates value conversions to the org.osgi.util.converter.Converter. However, JCR values will be wrongly processed by the Converter, since it will first convert them to maps and then return the map's key if the key's type is the same as the conversion type. For JCR values, the Map's keys will be the value's public method names, whereas the values will be the invocation of said methods. This is definitely not the behaviour we want.

The simplest solution would be to optionally import the javax.jcr API and, if present, add some custom rules based on javax.jcr.Value into the Converter.

Issue Links

• is caused by: SLING-8116 ValueMap - implement default methods using OSGI Converter
• links to: GitHub Pull Request #15