[
https://issues.apache.org/jira/browse/DAFFODIL-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220757#comment-17220757
]
Shashi Ramaka commented on DAFFODIL-2408:
-----------------------------------------
Yes. The schema has a defined list of names for properties and parameters. The
failing test files have names of properties or parameters not on those lists.
Updating the predefined list of names for properties and parameters should fix
that.
Also, the schema is parsing each line separately for parameter names and
values. Lines like these where the property and parameter names extend into the
next line (the second line starts with a tab) are not being parsed correctly.
{noformat}
ATTENDEE;CN="Handzel, Zachary (Peraton) (US Person)";ROLE=OPT-PARTICIPANT;R
SVP=TRUE:mailto:[email protected]{noformat}
> iCalendar schema + data causes Daffodil to abort
> ------------------------------------------------
>
> Key: DAFFODIL-2408
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2408
> Project: Daffodil
> Issue Type: Bug
> Affects Versions: 2.3.0, 2.7.0
> Reporter: Mike Beckerle
> Assignee: Shashi Ramaka
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: dfdl_2_3_ics_excep.zip
>
>
> A user is using Daffodil 2.3.0 with the iCalendar DFDL schema, and has
> provided an ".ics" file.
> These cause Daffodil 2.3.0 to fail with invariant failed.
> I have verified that these also cause problems (but not the same one) on
> Daffodil 2.7.0 with the latest iCalendar schema I have access to.
> On 2.7.0 Daffodil this aborts when run with a trace, and without a trace it
> parses producing an empty iCalendar element, without error. It doesn't even
> complain about not consuming the data. This is of course nonsense. There's
> plenty of data, and an empty icalendar element isn't valid. It has a required
> vcalendar child element. (You have to turn validation off to get the empty
> icalendar result, otherwise you get validation errors)
> Contact [~mbeckerle] for the associated files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
