[ 
https://issues.apache.org/jira/browse/OAK-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245637#comment-16245637
 ] 

Julian Sedding commented on OAK-6917:
-------------------------------------

bq. Nope, that doesn't work

A shame, but not entirely unexpected. Did you try changing the field's type to 
{{Map<String, Object>}}? That should work (at least with DS 1.3).

>From the Declarative Services 1.3 Spec, References to Services section 112.3.3 
>Field Strategy (OSGi R6 Compendium):
{quote}
For a reference with unary cardinality, a field must be of one of the following 
types:
...
Map - An unmodifiable Map containing the service properties of the bound 
service. This Map must additionally implement Comparable with the compareTo 
method comparing service prop- erty maps using the same ordering as 
ServiceReference.compareTo based upon service ranking and service id.
{quote}

> Configuration presets for DocumentNodeStoreService
> --------------------------------------------------
>
>                 Key: OAK-6917
>                 URL: https://issues.apache.org/jira/browse/OAK-6917
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.8
>
>         Attachments: OAK-6917-alternative-approach.patch, OAK-6917.patch
>
>
> When Oak is deployed in an OSGi container, applications usually want to ship 
> a default configuration which is different from the defaults present in Oak. 
> E.g. an application may want to use a default cache size of 1G for the 
> DocumentNodeStoreService instead of the default 256M. Now if a user of the 
> application provides a custom configuration and does not specify the cache 
> size, the value for this configuration will flip back to the Oak default of 
> 256M.
> There should be a way to configure presets for the application that are 
> different from the Oak defaults and then allow a user to customize the 
> configuration while still respecting the presets.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to