docs(opcua): fix stale NodeWriteRouter reference in EnsureVariable comment
v2-ci / build (push) Failing after 40s
v2-ci / unit-tests (tests/Core/ZB.MOM.WW.OtOpcUa.Cluster.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.ControlPlane.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Runtime.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Security.Tests) (push) Has been skipped
v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.Host.IntegrationTests) (push) Has been skipped
v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.IntegrationTests) (push) Has been skipped
v2-ci / build (push) Failing after 40s
v2-ci / unit-tests (tests/Core/ZB.MOM.WW.OtOpcUa.Cluster.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.ControlPlane.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Runtime.Tests) (push) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Security.Tests) (push) Has been skipped
v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.Host.IntegrationTests) (push) Has been skipped
v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.IntegrationTests) (push) Has been skipped
This commit is contained in:
@@ -850,7 +850,7 @@ public sealed class OtOpcUaNodeManager : CustomNodeManager2
|
|||||||
};
|
};
|
||||||
// Task 11: a writable equipment tag owns an inbound-write handler. The SDK invokes
|
// Task 11: a writable equipment tag owns an inbound-write handler. The SDK invokes
|
||||||
// OnWriteValue on a client write; it gates on the WriteOperate role and routes to the backing
|
// OnWriteValue on a client write; it gates on the WriteOperate role and routes to the backing
|
||||||
// driver via NodeWriteRouter. Read-only nodes leave it null (the default) so a write is
|
// driver via NodeWriteGateway. Read-only nodes leave the handler unattached so a write is
|
||||||
// rejected by the SDK's own AccessLevel check before it ever reaches a handler.
|
// rejected by the SDK's own AccessLevel check before it ever reaches a handler.
|
||||||
if (writable)
|
if (writable)
|
||||||
{
|
{
|
||||||
|
|||||||
Reference in New Issue
Block a user