Curl to create OsigConfig nodes
I have two questions:
1) When I apply settings via the felix console, they get saved as nodes of nt:file with a jcr:content node underneath. I see everywhere else to use osgiconfig nodes instead. Which one of the two is preferred when setting these configurations using curl
2) I have issues creating nodes underneath a parent node of the format: config.author or map.publish if there already is a config or map node. Sling is just mapping my request to config / map, rather than config.author / map.publish. Anyone any idea how I can work around this?
Many thanks,
Katrien