You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2021/03/29 15:45:00 UTC
[jira] [Resolved] (DAFFODIL-774) Improve detection of disallowed
entities in property values
[ https://issues.apache.org/jira/browse/DAFFODIL-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Lawrence resolved DAFFODIL-774.
-------------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
Fixed in commit 50326941f91e3fc65edf4765e6139fb98ddf349c
> Improve detection of disallowed entities in property values
> -----------------------------------------------------------
>
> Key: DAFFODIL-774
> URL: https://issues.apache.org/jira/browse/DAFFODIL-774
> Project: Daffodil
> Issue Type: Bug
> Components: General
> Reporter: Steve Lawrence
> Assignee: Regis Thomas
> Priority: Major
> Labels: beginner
> Fix For: 3.1.0
>
>
> In RuntimePropertyMixins.scala, many checks are done to make sure various character entities aren't in the data, for example:
> {code}
> this.schemaDefinitionUnless(!s.contains("%NL;"), "textStandardDecimalSeparator cannot contain NL")
> {code}
> Because this just does String.contains, it doesn't take into account character entities that were escaped. For example, the following would be incorrectly considered a schema definition error:
> {code}
> textStandardInfinityRep="%%NL;"
> {code}
> Checks should be performed using the EntityReplacer
--
This message was sent by Atlassian Jira
(v8.3.4#803005)