poi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 56384] [PATCH] Nested Field Codes are not parsed correctly
Date Thu, 12 Mar 2015 21:11:54 GMT

Josh Holthaus <josh.holthaus@gmail.com> changed:

           What    |Removed                     |Added
             Status|NEEDINFO                    |NEW

--- Comment #3 from Josh Holthaus <josh.holthaus@gmail.com> ---
I am basically redoing the iteration in the parseFieldStructureImpl method. The
current switch statement will ignore a field code if a second FIELD_BEGIN_MARK
is encountered before a FIELD_END_MARK. Example: { OUTER_FIELD { INNER_FIELD
}}. In this case the OUTER_FIELD would be ignored because the start of the
INNER_FIELD occurs before the OUTER_FIELD is closed. I changed the method to
store all the begin marks in a list to retain their order when fields are
nested. When a FIELD_END_MARK is encountered I take the last FIELD_BEGIN_MARK
and corresponding FIELD_SEPARATOR_MARK and add them to the results. I no longer
needed the binarySearch method to determine the next start since I changed it
to iterate through all fields between startOffsetInclusive and

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org

View raw message