https://issues.apache.org/jira/browse/DAFFODIL-2183
I created this ticket for the unparser bug.
From: Costello, Roger L.
Sent: Tuesday, July 16, 2019 10:51:50 AM
To: users@daffodil.apache.org
Subject: RE: [EXT] Re: Unable to parse an in-band nil on complex type
I am using the latest release, 2.4.0
From: Beckerle, Mike
Sent: Tuesday, July 16, 2019 10:47 AM
To: users@daffodil.apache.org
Subject: [EXT] Re: Unable to parse an in-band nil on complex type
What release of Daffodil?
2.4.0 or earlier?
From: Costello, Roger
What release of Daffodil?
2.4.0 or earlier?
From: Costello, Roger L.
Sent: Tuesday, July 16, 2019 10:43:38 AM
To: users@daffodil.apache.org
Subject: Re: Unable to parse an in-band nil on complex type
Thanks Mike. I made the changes you described. Now parsing
Subject: [EXT] Re: Unable to parse an in-band nil on complex type
The initiator must be on the person element, not on the interior sequence,
since that interior sequence will never even be attempted to parse when the
DFDL processor finds the nil representation of the surrounding complex element
ms like the unparser may
have a bug having to do with nilled complex elements, or empty string elements.
Not sure.
From: Costello, Roger L.
Sent: Tuesday, July 16, 2019 7:47:53 AM
To: users@daffodil.apache.org
Subject: Re: Unable to parse an in-band nil on comple
What am I doing wrong, please?
/Roger
From: Beckerle, Mike
Sent: Monday, July 15, 2019 11:14 AM
To: users@daffodil.apache.org
Subject: Re: Unable to parse an in-band nil on complex type
The nil representation is preferred to any other representation, which is to
say that the parser checks f
The nil representation is preferred to any other representation, which is to
say that the parser checks for the nil representation first before attempting
to parse any other representation.
So if %ES; is the nil value, and there is no initiator nor terminator in the
nil representation (based o
