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 2023/06/09 20:32:00 UTC

[jira] [Updated] (DAFFODIL-2813) Schematron URIResolver uses Classpath rather than Daffodil Resolver

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

Steve Lawrence updated DAFFODIL-2813:
-------------------------------------
    Priority: Critical  (was: Major)

Bumping this to critical since the fix for DAFFODIL-2820 runs into this bug, and this should be a simple fix.

> Schematron URIResolver uses Classpath rather than Daffodil Resolver
> -------------------------------------------------------------------
>
>                 Key: DAFFODIL-2813
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2813
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 3.4.0
>            Reporter: Olabusayo Kilo
>            Priority: Critical
>
> The schematron URIResolver requires the project to be on the classpath in order for it to successfully resolve includes/imports.
>  
> It should use the Daffodil Resolver so the workaround of putting stuff on the classpath isn't necessary.



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