BTW: Daffodil version 2.2.0 should have changed this to Int.MaxValue, i.e., 2Gig occurrences.
So you have to tune it downward to something sensible, instead of upward. Is your failure with 2.2.0, or an earlier version. If 2.2.0 it's a bug and I'd like to isolate it better. 2.2.0 is now the current release and is available on maven central. ________________________________ From: Gedvilas, Brett L2 <[email protected]> Sent: Friday, September 28, 2018 4:49:38 PM To: [email protected] Subject: Re: MaxOccurs Limit Ah thank you, I didn't realize the tunables were accessible as a command line option. ________________________________ From: Mike Beckerle <[email protected]> Sent: Friday, September 28, 2018 12:15:10 PM To: [email protected] Subject: Re: MaxOccurs Limit This is a tunable limit. I am not near my computer right now, but you should be able to find guidance about setting this tunable by searching. I will check back later this evening to see if you are still stuck. -------- Original message -------- From: "Gedvilas, Brett L2" <[email protected]> Date: 9/28/18 1:45 PM (GMT-05:00) To: [email protected] Subject: MaxOccurs Limit Hi, I keep running into a parsing error relating to the maximum number of occurrences for an element in my schema. The exact error is shown below: [error] Parse Error: Evaluation of occursCount expression (dafint:OccursCountEv@8df0b3, runtime) returned out of range value 4096. For context, the schema evaluates an expression to determine the occurrences of the element. The length of the element is 16 bits and should repeat based on a previously parsed value as shown: <xs:element name="sample" type="xs:unsignedInt" dfdl:length="16" minOccurs="0" maxOccurs="unbounded" dfdl:occursCountKind="expression" dfdl:occursCount="{ ../num_on_pulse_samples }" /> As far as I can tell daffodil limits the occurrences of an element to 1024, is this an implementation-defined maximum or is there any type of work-around for this limit? Thanks! Brett
