[jira] [Resolved] (OAK-776) NodeState convenience accessors

["Jukka Zitting (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved OAK-776.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.13)
                   0.11

The following convenience accessors are now available:

* {{getBoolean()}}
* {{getLong()}}
* {{getString()}}
* {{getName()}}
* {{getNames()}}

They seem to cover by far the most common access patterns so resolving this as Fixed.


> NodeState convenience accessors
> -------------------------------
>
>                 Key: OAK-776
>                 URL: https://issues.apache.org/jira/browse/OAK-776
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.11
>
>
> One of the original goals in designing the NodeState interface was to avoid too many convenience accessors to keep the interface simple and easily to decorate with things like the SecureNodeState wrapper. Since then convenience code like type-specific property value accessors have been added in various places as ad-hoc static utility methods.
> Now that the overall NodeState design is mostly fixed, the set of NodeState implementations mostly known and we have a good idea of the common NodeState access patterns, I think it would be useful to add various convenience methods like {{hasProperty(String)}} or {{getBoolean(String)}} that allow us to both simplify commonly occurring client code and further optimize the SegmentNodeState class without requiring it to cache fully loaded PropertyState instances in memory.



--
This message was sent by Atlassian JIRA
(v6.1#6144)