I would like to see this somewhat separated from the JCR and to have a more similar data structure to Resources and ValueMaps (Resource-lite?). This may actually be a really interesting concept for import jobs where you could create the data structure you are importing and just "apply" it over a repository tree instead of doing individual checks.
On Tue, Mar 14, 2017 at 7:44 AM, Stefan Seifert <sseif...@pro-vision.de> wrote: > >> 4. think about making a variant of the TestUtil.getDeep() method > >available in the API as well - it was already duplicated in fsresource > > > >Please see my feedback on http://www.mail- > >archive.com/dev@sling.apache.org/msg65486.html. I don't think using > >Map<String, Object> is the proper return type here. > > you're right, i've missed that comment. > > nested maps are dead simple, but perhaps not enough here. first i thought > same node name and property name is a variant of same-name-sibling (which > is only partial supported even by oak), but this does not seem to be the > case. so i do not think we have to support same name siblings, but same > node name and property name. > > i will propose a new approach. > > stefan > > >
