[jira] [Resolved] (DAFFODIL-1519) occursCount that is greater than maxOccursBounds causes PE/UE rather than SDE

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

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

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

Fixed in 62da5b5a44e3f90c42ed446f7e64950ff61b6738

> occursCount that is greater than maxOccursBounds causes PE/UE rather than SDE
> -----------------------------------------------------------------------------
>
>                 Key: DAFFODIL-1519
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1519
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End, Diagnostics, Usability
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 2.2.0
>
>
> Currently, if you have an expression for occursCount, and that expression results in a value greater than maxOccursBounds (which defaults to 1024), then we currently throw a PE/UE. When parsing, this can result in backtracking for a non-obvious reason. The fact that maxOccursBounds was exceeded may not even be reported.
> Instead, it seems like this should instead be a SDE so that the error is reported immediately and the user can either modify a tunable to increase the maxOccursBOunds, or rework the schema to not need such a large array.



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