Log In
Home
09/11/2015
Offline
I have a UA client that is browsing a server. When I get the TargetNodes from a particular SourceNode, it is returning 2 TargetNodes with the same NodeId. One is an Object and one is a Variable. Is this allowed? I cannot find anything in the spec that says one way or the other.
05/30/2017
Offline
NodeIds identify one Node.
A Node may have many NodeIds
The NodeId Attribute always returns the canonical NodeId.
Sounds like this server is not compliant.
09/11/2015
Offline
Let me make sure I understand what you are saying. It is not legal to have the same NodeId more than one place in the address space. If the same “Node” exists in more than place in the address space, the references must point to the exact same node. If the node is an alias of some kind so it isn’t exactly the same, then it must have a different NodeId. In my customers case, they have a reference to a Node that has a Node class of Variable and a separate reference to a Node that has a Node class of Object, but both Nodes have the same NodeId and they both have the same child references. So that is a violation of the spec. Is this correct?
Let me try to be more specific. When we call browse for forward references on a particular NodeId, we get back 2 references. They both have the same BrowseName and the same NodeId. The difference is they have different NodeClasses. Based on the above discussion, I am thinking this is not allowed.
05/30/2017
Offline
Yes that is not allowed. 2 different NodeClasses mean 2 different Nodes with the same NodeId.
What would happen if the ‘Value’ or ‘EventNotifier’ attribute is read?
It makes no sense. I suspect it is simply bug in the server where the NodeClass is set incorrectly
1 Guest(s)
Usage Policy