eclipse-aascw / aas-core-codegen / 35322804807

90%

push

github

Fix the XSD lexical forms in the Java XML (#719)

The Java xmlization neither wrote nor read the lexical forms which
`xs:double` and `xs:boolean` prescribe, so a document written by any
other SDK could not always be read back, and a document Java wrote could
not always be read by them.

A double went out through `writeStringifiedContent`, which is to say
through `Double.toString`, which renders an infinity as `Infinity`.
`xs:double` spells it `INF`.

Reading was wrong in both directions at once. `Double.valueOf` refuses
`INF` and `-INF` -- while accepting `Infinity`, a trailing type suffix
as in `1.0d`, a hexadecimal significand as in `0x1p3`, and surrounding
whitespace, none of which is a valid `xs:double`.

`xs:boolean` has four literals and not two: `1` and `0` are as good as
`true` and `false`. Java refused them. Mind that `Boolean.valueOf`
can not be used to widen this: it answers `false` to anything which is
not `true`, so it would have taken `0` and `banana` alike, and silently.
The four literals are matched explicitly, and they stay case-sensitive.
`TRUE` is not a valid `xs:boolean`.

6 of 6 new or added lines in 1 file covered. (100.0%)

34764 of 40511 relevant lines covered (85.81%)

2.57 hits per line