[ https://issues.apache.org/jira/browse/SLING-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632676#action_12632676 ]
Felix Meschberger commented on SLING-602: ----------------------------------------- Ok, so we ignore data loss. But instead of just using the data type's min or max value in case of an under- or overflow, I would just use the standard Java mechanism used by down casting. > ValueMap#get(java.lang.String name, T defaultValue) should support Integer > -------------------------------------------------------------------------- > > Key: SLING-602 > URL: https://issues.apache.org/jira/browse/SLING-602 > Project: Sling > Issue Type: Wish > Components: JCR Resource > Affects Versions: JCR Resource 2.0.4 > Environment: Windows XP, Sling Version 2.0.3-incubator-SNAPSHOT > (running of Communiqué5) > Reporter: Andreas Vogl > Assignee: Felix Meschberger > Priority: Minor > > Hi, > Working with the sling API, I've been using the ValueMap class rather > frequently: > org.apache.sling.api.resource.ValueMap > I noticed that the type java.util.Lang is supported for the getter methods, > but the type java.util.Integer is apparently not supported. > The getter methods i am referring to: > <T> T get(java.lang.String name, java.lang.Class<T> type) > <T> T get(java.lang.String name, T defaultValue) > > Personally I would find it very convenient to be able to pass integers as > default values and also get an integer as return type. > Apart from the convenience aspect, the lack of Integer support is really a > source for bugs: It's intuitive to pass Integers - it will compile fine but > not work in the end. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.