As part of
 https://issues.apache.org/jira/browse/SLING-8116

Which came about in the comments for
https://issues.apache.org/jira/browse/SLING-7934

I discovered that the Converter works differently then our current rules for 
handling conversions in the ValueMap.

Supports conversions to an array of primitive types
valueMap.put("prop1", new String[] { "12", "2" });
valueMap.get("prop1", int[].class) -> returns a populated int[]

Supports arrays to scalar
valueMap.put("prop1", new String[] { "12", "2" });
valueMap.get("prop1", int.class) -> returns the Integer 12

These are just the two I have identified. There is mostly likely a few more 
subtle differences on top of this.
After reviewing the Converter, I believe that this would be an invaluable 
addition to the framework, but that comes with a cost of handing off the rules 
of conversion to a separate utility.

If anyone has issues with this, say it now.

- Jason

Reply via email to