[jira] [Resolved] (DAFFODIL-1477) ES now allowed in terminator - causes a test to fail now.

["Steve Lawrence (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAFFODIL-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence resolved DAFFODIL-1477.
--------------------------------------
    Resolution: Fixed

Fixed in commit 48ad264405690e15788fca74c14ed75b2fd952b4

> ES now allowed in terminator - causes a test to fail now.
> ---------------------------------------------------------
>
>                 Key: DAFFODIL-1477
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1477
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End, General
>    Affects Versions: 2.0.0
>            Reporter: Michael Beckerle
>            Assignee: Steve Lawrence
>            Priority: Blocker
>             Fix For: 2.4.0
>
>
> In accordance with the DFDL v1.0 spec change to terminator, 
> If we remove the check for %ES; from the code for terminator, then  test
> test_entity_fail_03 fails with:
> Parse Error: Term('CompiledExpression(: %ES;)') - element.a: Found delimiter (,) for element.root::LocalComplexTypeDef::sequence when looking for Term(<DFA lookingFor=':' /> <DFA lookingFor='%ES;' /> <DFA lookingFor=',' />) for element.root::LocalComplexTypeDef::sequence::element.a before element.b
> Schema context: element.a Location line 100 column 12 in file:/tmp/sch39093359406659818781.dfdl.xsd
> Data location was preceding byte 1 limit(bytes) 3
> It isn't handling the case where the separator of the sequence is found, not the terminator, because one of the list of terminators is ES, which effectively makes that terminator optional.
> We may simply want to put back in the restriction that prohibits ES from terminators altogether.
> For now I have moved this test to scala-debug



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)