You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2008/11/04 15:28:44 UTC
[jira] Commented: (SLING-719) Node-based configs for jcrinstall
[ https://issues.apache.org/jira/browse/SLING-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644971#action_12644971 ]
Bertrand Delacretaz commented on SLING-719:
-------------------------------------------
Work in progress implementation committed in revision 711260
A node like this one, found in a folder watched by jcrinstall:
curl http://localhost:7402/org.apache.sling.SomeConfig.cfg.tidy.2.json
{
"somevalue": "here",
"jcr:primaryType": "nt:unstructured",
"foo": {
"somevalue": "bar",
"jcr:primaryType": "nt:unstructured"
}
}
Will cause an OSGi config with pid = "org.apache.sling.SomeConfig" to be created, with a single somevalue=here property.
The node name must end with .cfg and the node type must be nt:unstructured.
If the node has a child like "foo" in the example, its properties override the ones of the main mode if the "foo" runmode (provided by the RunMode service) is active, to provide for runmode-dependent configurations.
The code needs more automated tests for those new features.
> Node-based configs for jcrinstall
> ---------------------------------
>
> Key: SLING-719
> URL: https://issues.apache.org/jira/browse/SLING-719
> Project: Sling
> Issue Type: Improvement
> Components: JCR Install
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> Besides the existing .cfg file format, having node-based configurations would make them more granular and easier to patch.
> I'll implement an additional config source for jcrinstall, that uses nodes and properties (including multi-value, and taking property types into account).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.