Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Companion Ticket for JiraserverASF JIRAcolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId5aa69414-a9e9-3523-82ec-879b028fb15bkeyPage for SLING-6420

Planned Current rules for Object Conversion in Value Maps that should be applied to both implemented in API ValueMapDecorator and to JCR ValueMap implementation. 

Rules for single values

 
Rule / Already supported by:API 2.16.2
ValueMapDecorator
jcr.resource 2.9.2
ValueMap
   
   
 
Any Object -> String (via toString)(tick)(tick)
String or any Number type -> Integer and vice versa(tick)(tick)
String or any Number type -> Long and vice versa(tick)(tick)
String or any Number type -> Double and vice versa(tick)(tick)
String -> Boolean and vice versa(tick)(tick)
Convert any number type of (Long, Byte, Short, Integer, Double, Float, BigDecimal) -> to each of them or String and vice versa(warning) currently missing(tick)
Convert any date type of (Calendar, Date) -> to each of them or String and vice versa(warning) currently missing(tick)

Convert any type of (Long, Byte, Short, Integer, Double, Float, Calendar, Date, Boolean, BigDecimal) -> to each of them - including exotic conversion like Boolean to Date

(error) we do not want to support the conversion that make less sense

(tick)

Rules for Arrays

  • Convert single value to singleton array if array is requested
  • Convert array types if conversion is supported for the type of the array elements