[
https://issues.apache.org/jira/browse/PLC4X-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17368731#comment-17368731
]
Christofer Dutz commented on PLC4X-301:
---------------------------------------
Ok ... I created a testcase that reproduces the problem.
Problem now is however: How to we separate the type definition from the rest of
the query? If I simply ensure the optional type is the last colon-separated
part this would work in your case as you have "." in the part after the last
colon, but if your query was:
{code:java}
ns=6;s=::AsGlobalPV:ProductionOrder
{code}
Then it would interpret "ProductionOrder" as type and I don't think that's
good. So I see two options:
1) We make the type mandatory
2) We use a different separator, but in that case we need one that it not
allowed in OPC-UA query strings
Making it mandatory seems sub-ideal as in most cases it is probably not needed.
Making it mandatory breaks the similarity to other drivers. Perhaps [~hutcheb]
can help with this?
> 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)
