Log In
Register
Topic RSS
18:57, EEST
February 21, 2014
Offline
Hi,
I often need to delete a complete hierarchy of dynamically created nodes. The NodeManagerUaNode.deleteNode(…) would in principle do a perfect job, just it only considers “HasChild” relationships, which leaves “Organized” nodes untouched. The semantics of Organizes is similar to HasChild (IMO – for this purpose). Would you think that it might make sense to add “Organizes” relationships to be considered by NodeManagerUaNode.deleteNode()?
Thanks to using Kotlin, I was able to extend the NodeManagerUaNode’s with this capability; but it would certainly be nice to have it natively available in NodeManager.
Thanks,
Hans-Uwe
10:35, EEST
April 3, 2012
Offline
Hi,
We could maybe consider an overload for taking ReferenceTypeIds.
In general using other than HasChild without knowing the context could end up deleting more that was intended. The spec for Organizes:
“The semantic of this ReferenceType is to organise Nodes in the AddressSpace. It can be used
to span multiple hierarchies independent of any hierarchy created with the non -looping
Aggregates References.
The SourceNode of References of this type shall be an Object or a View. If it is an Object then
it should be an Object of the ObjectType FolderType or one of its subtypes”
But the spec for HasChild instead is:
“The semantic i s to indicate that References of this type span a non -looping hierarchy.
Starting from Node “A” and only following References of the subtypes of the HasChild
ReferenceType it shall never be possible to return to “A”. But it is allowed that following the
References there may be more than one path leading to another Node “B”.”
So e.g. for an Instance that would e.g. refer to type nodes with Organizes (e.g. https://forum.prosysopc.com/fo…..odeset-xml), following and deleting Organizes targets would end up deleting those types also.
20:45, EEST
February 21, 2014
Offline
I do see the point you made. Even though the DI application example is a bit ‘exotic’, the use case does exist indeed.
Meanwhile I wrote a custom “deleteWithChildren(…)” method which browses for HasChild and Organizes reference targets recursively. (pretty similar to the SDK methods).
Thanks,
Hans-Uwe
1 Guest(s)
