You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Dave Thompson (Jira)" <ji...@apache.org> on 2023/09/13 14:58:00 UTC

[jira] [Closed] (DAFFODIL-2840) Relative include/import schemaLocations should not be resolved absolutely

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

Dave Thompson closed DAFFODIL-2840.
-----------------------------------

Closed as duplicate of ticket DAFFODIL-2828, per dev team.

> Relative include/import schemaLocations should not be resolved absolutely
> -------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2840
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2840
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Front End
>            Reporter: Steve Lawrence
>            Priority: Major
>             Fix For: 3.5.1
>
>
> If a schemaLocation path is relative, then it should only be found relative to the importing schema. Only absolute schemaLocation paths search the classpath. Currently, if a schemaLocation path does not start with a /, it will append one and look on the classpath. This makes it ambiguous if a path should be looked up relative to the importing file or if it should be found on the classpath. This can cause extra complexity down the line.
> Note that we may want to fallback to this behavior if a include/import is not found relatively, and output a warning, since many schemas do expect this behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)