[
https://issues.apache.org/jira/browse/PLC4X-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125603#comment-17125603
]
Christofer Dutz commented on PLC4X-202:
---------------------------------------
Hi,
well we have the same problem with all other drivers too ... what we currently
do, if you want an unsigned, PLC4X uses the next bigger type ... so if you're
reading an "unsigned byte" we'll use a short instead ... I would suggest to do
the same as if we started using these Milo types we would loose one of the
major benefits of PLC4X ... the independence from one driver/protocol.
> OPC-UA Driver cannot write Unsigned Types
> -----------------------------------------
>
> Key: PLC4X-202
> URL: https://issues.apache.org/jira/browse/PLC4X-202
> Project: Apache PLC4X
> Issue Type: Bug
> Components: Driver-OPC-UA
> Affects Versions: 0.7.0
> Reporter: Alessandro Rossignoli
> Priority: Major
>
> Currently, unsigned types are not supported in writing direction from the
> driver although they are fully supported by Eclipse Milo and in reading.
> Actually I have applied a modification and tested it to be able to support
> these types. It is kind of the same patch applied for BigIntegers but done
> introducing UShort and UInteger from Eclipse Milo.
> The downside is that every driver will use the Eclipse Milo types, being the
> JVM missing unsigned types. I don't know if you have a better solution or if
> using Milo types in all the drivers is acceptable for you.
> I am open for suggestions :)
>
> (PS. when I will complete all the testing I will create 3 separate PR for
> issue #200, #201 and this one)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
