[
https://issues.apache.org/jira/browse/SLING-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600048#comment-13600048
]
Carsten Ziegeler commented on SLING-2779:
-----------------------------------------
I think we shouldn't define the resource property sling:defaults - just a
simple way of creating a value map with the desired behaviour.
I'm fine with providing a DefaultsValueMap which gets passed a map of default
values, so a constructor with two value maps. But I think we shouldn't
implement the sling:defaults mechanism, this can easily be done by getting the
resource defined by the "defaults" property and adapting it to a value map. But
it frees the client code from using a predefined mechanism.
> Support for default properties values of a resource
> ---------------------------------------------------
>
> Key: SLING-2779
> URL: https://issues.apache.org/jira/browse/SLING-2779
> Project: Sling
> Issue Type: New Feature
> Components: API
> Affects Versions: API 2.3.0
> Reporter: Gilles Knobloch
> Attachments: DefaultsValueMap.java
>
>
> I already noticed several times it would be useful to be able to specify a
> default properties for a resource:
> * if the resource itself contains the property, it will override the default
> one.
> * but if it doesn't, the default value is used.
> This could be done either via:
> * specifying a {{sling:defaults}} property on the resource, which contains
> the path to the resource which properties will be used by default.
> * providing a default map of properties
> Attaching a patch for review.
> For testing purpose, I put it under {{org.apache.sling.defaults}}, but I
> imagine it could go to {{org.apache.sling.api.resource}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
