[
https://issues.apache.org/jira/browse/DAFFODIL-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence updated DAFFODIL-1392:
-------------------------------------
Description:
Update: the original description of the issue was inaccurate. See the latest
comments for the underlying issue.
Issue with escapeEscape character that is first and precedes an escape-block
start.
It is being removed, but should be preserved as it does not precede an escape
character, nor an escape block end.
See test_BA000 in daffodil-test-ibm1
was:
Issue with escapeEscape character that is first and precedes an escape-block
start.
It is being removed, but should be preserved as it does not precede an escape
character, nor an escape block end.
See test_BA000 in daffodil-test-ibm1
Summary: escapeBlockStart partial match incorrectly drops characters
(was: escapeEscape character removed if first char before escape block start)
After some investigation, I've determine this actually does not have anything
to do with the EEC character. The issue is if scanning for an escapeBlockStart
does not find the escapeBlockStart (i.e. the field is not escaped), but it does
find a partial prefix match then the partial match is accidentally lost and
does not end up in the infoset.
For example, if dfdl:escapeBlockStart="XYZABC" and the data is "XYZfoo" (i.e.
the string is not escaped), the infoset will incorrectly contain "foo" instead
of "XYZfoo".
The confusion with EEC came because in the mentioned test the EEC happened to
be a prefix of the escapeBlockStart, so it seemed related but was actually just
a coincidence.
I have updated the issue summary to reflect the actual issue.
> escapeBlockStart partial match incorrectly drops characters
> ------------------------------------------------------------
>
> Key: DAFFODIL-1392
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1392
> Project: Daffodil
> Issue Type: Bug
> Components: Back End, General
> Affects Versions: 2.0.0
> Reporter: Mike Beckerle
> Assignee: Steve Lawrence
> Priority: Major
> Fix For: 4.1.0
>
>
> Update: the original description of the issue was inaccurate. See the latest
> comments for the underlying issue.
> Issue with escapeEscape character that is first and precedes an escape-block
> start.
> It is being removed, but should be preserved as it does not precede an escape
> character, nor an escape block end.
> See test_BA000 in daffodil-test-ibm1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
