When thinking about it a bit longer I came to the same explanation...
but according to my tests this is not entirely correct. It is _not_
sufficient if the node has a nodedata "name":
I changed my code so that when creating the data node at the same time
a nodedata "name" was created. The node then showed up correctly in
the the data module's JCR browser including the "name" nodedata. But
editing it with the standard gui dialog for that node type still
always renamed the node.
So it's not only that the node must have a "name" node data set to the
same value as the node's name itself, but the gui dialog for the node
must contain a "name" control of the type "edit". Otherwise the name
of the node is changed!
So my questions now would be:
- Could it be that the data module gui dialogs do not check if the
nodes already have "name" nodedata?
- Couldn't one simply use the node's name to be displayed in the list
and therefore there the "name" nodedata would not be mandatory anymore?
-will
On 26.06.2008, at 12:43, Jan Haderka wrote:
Hi Will,
the nodeData "name" is used to identify the item when displayed in the
tree. For that reason we always need it to be able to display entry in
the tree. When nodeData "name" is missing, it is assumed that such
entry
have been created by importer (or by something else programatically)
and
value defaulted to the name of the node type.
Cheers,
Jan
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
