[
https://issues.apache.org/jira/browse/DAFFODIL-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714653#comment-17714653
]
Steve Lawrence commented on DAFFODIL-2802:
------------------------------------------
Potentially related to DAFFODIL-2499? Either separatorSuppressionPolicy="never"
was either never fully implemented or is just currently broken. Note that our
unsupported page currently lists separatorSuppressionPolicy="never" as
unimplemented.
This PR merged tests that show a number of places where SSP Never is broken:
https://github.com/apache/daffodil/pull/537. Fixing those might fix this issue.
Note that that bug claims SSP Never is minor priority (with major priority to
add a diagnostic), but maybe it is now needed if there is no other way to
implement this format?
Is a potential workaround to make ie3 and se5 mandatory (i.e. minOccurs="1"),
but just allow them to have empty values? I guess ie3 is an int so cannot have
a zero length and that is the reason for it's optionality?
> Array with optional element followed by scalar optional element drops
> separator
> -------------------------------------------------------------------------------
>
> Key: DAFFODIL-2802
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2802
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 3.4.0
> Reporter: Olabusayo Kilo
> Priority: Blocker
> Fix For: 3.5.0
>
> Attachments: TestSeparatorSuppression.scala, suppressedseparator.tdml
>
>
> An array with a trailing optional element followed by a scalar optional
> element loses a separator when both elements are missing during an unparse.
> The trace indicates, there's a
> SuppressableSeparatorUnparserSuspendableOperation for the scalar element (se5
> in the example schema). My initial guess was that the last element in the
> array was being treated as a trailing element, but we need it to not be
> treated that way.
>
> For completeness, you get the following error from TDML on the 2nd test
> {noformat}
> output data length 12 for '/1/2/3.5//6
> ' doesn't match expected length 13 for '/1/2/3.5///6
> '{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
