Topic RSS9:44, EET
November 17, 2014
OfflineHello,
I am noticing something strange (possibly caused by my misuse of the SDK). I have generated some Java Code and am now performing the following:
MemberTypeNode node = nodeManager.createInstance(MemberTypeNode.class,newMemberNodeId,browseName,displayName);
Now for some reason the NodeId of the node’s data type has an index that does not match the namespace defined in the TypeDefinitionId (but instead that of the application uri).
Please see here: https://gist.github.com/o1iver…..f097462ddc.
Current override, maybe this helps: https://gist.github.com/o1iver…..roblem-log
Thanks!
Oliver
13:22, EET
April 3, 2012
OfflineSeems we have a bug. The NodeId in the xml is not mapped to “global” NodeId in case of DataType (since the NodeIds in the xml point 0=standardNameSpace 1->=The namespace defined in NamespaceUris part at the start of the xml) and instead pointed directly to 1 in global namespace. I can send a beta link by mail after this is fixed.
1 Guest(s)

Log In
Register