You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@plc4x.apache.org by "Matthias Milan Strljic (Jira)" <ji...@apache.org> on 2021/06/25 11:45:00 UTC

[jira] [Comment Edited] (PLC4X-301) OPCUA address identifier with colon will not work

    [ https://issues.apache.org/jira/browse/PLC4X-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369420#comment-17369420 ] 

Matthias Milan Strljic edited comment on PLC4X-301 at 6/25/21, 11:44 AM:
-------------------------------------------------------------------------

As Mentioned my solution would be to change the delimiter from ":" to ";" in the hope, that there will be no conflict because it is already a reserved character for the OPC UA namespace string. As [~torsten.uhr@sql-ag.de] also already mentioned.


was (Author: nalim2):
As Mentioned my solution would be to change the delimiter from ":" to ";" in the hope, that there will be no conflict because it is already a reserved character for the OPC UA namespace string

> OPCUA address identifier with colon will not work
> -------------------------------------------------
>
>                 Key: PLC4X-301
>                 URL: https://issues.apache.org/jira/browse/PLC4X-301
>             Project: Apache PLC4X
>          Issue Type: Bug
>          Components: Driver-OPC-UA
>    Affects Versions: 0.8.0
>            Reporter: Torsten
>            Priority: Major
>
> If a field address has an identifier like „ns=6;s=::AsGlobalPV:dsMES.Read.ProductionOrder“, the colons in the field identifier does not match to the Regex in  org.apache.plc4x.java.opcua.protocol.OpcuaField.
> Such fields are not accesable at the moment.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)