On Fri, Jul 6, 2012 at 11:44 AM, Carsten Ziegeler <cziege...@apache.org> wrote: > Yepp, so I guess going with 2) is the better option, however this > would require something like a add(Resource parent, String > childNodeName, Map props) on the resource resolver. > > So maybe we go the same route as we did with getParent(), listChildren > and add the functionality to the resource resolver but provide > convenience methods on the resource which just delegate...
Sounds good to me, and it's consistent with what we already have. -Bertrand
