Hello,
I am overhauling our test suite using the RC3 release and gladly found that several issues are now gone away. The unparse process is still giving me some problems though and I want to share one particular one with you, hoping for some advice or assistance.
I attached this as "Example_wiki_folio_raw.edi".When I parse this using Smooks the result is what I attached as "Example_wiki_folio_infoset.edi". Now when I try to unparse it again I receive an exception (attached as "exception_trace.txt").
The interesting part is:
Caused by: org.apache.daffodil.japi.DaffodilUnparseErrorSAXException: Runtime Schema Definition Error: Non-empty string required.
Schema context: sequence[1] Location line 391 column 11 in .../ceb0086d965a9d43ef05c51d5f231a50d77efa6c/edifact-schemas-2.0.0-RC3-d96a.jar!/d96a/EDIFACT-Segments.dfdl.xsd
Which refers to this schema part:
<xsd:element name="CUX-Currencies" type="D96A:CUX-Currencies"/>
<xsd:complexType name="CUX-Currencies">
<xsd:sequence dfdl:ref="ibmEdiFmt:EDISegmentSequenceFormat">
<xsd:sequence dfdl:ref="ibmEdiFmt:EDISegmentPartRepeatSequenceFormat">
<xsd:element dfdl:nilKind="literalValue"
dfdl:nilValue="%ES;"
dfdl:useNilForDefault="no"
maxOccurs="2"
minOccurs="0"
name="C504"
nillable="true"
type="D96A:C504-CurrencyDetails"/>
</xsd:sequence>
When I remove the CUX element entirely from the sample file, the issue pops up again for another segment (but again refering to a sequence).
Maybe you could try whether you can reproduce this which would confirm it is a bug.
Thanks in advance,
Axel