On Thu, Aug 20, 2009 at 3:01 PM, Jukka Zitting<[email protected]> wrote: > * The name of a node is unique among the child nodes of the same > parent unless the same-name-siblings option is been enabled in the > relevant node type.
Note that in this case the application has to set the node name and will get an exception upon a conflict and must handle the conflict itself. Solutions to that are a) creating new node names in a loop until no conflict is present (ie. appending a number), which works well in 99.9% of the situations or b) using node locking (of the parent node) to avoid conflicts in general (but this has its other issues). Regards, Alex -- Alexander Klimetschek [email protected]
