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 2022/11/03 13:34:00 UTC

[jira] [Closed] (DAFFODIL-2616) End-user doc of how import/include schemaLocation resolver works

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

Dave Thompson closed DAFFODIL-2616.
-----------------------------------

Verified the specified commit (commit 22f81e88b0b8570a199deaa748e23cf69577ed58) is included in the latest pull (rc2) from the daffodil repository.

Verified that the difference between the javadoc and scaladoc pages was corrected and updated on the Apache Daffodil site.

> End-user doc of how import/include schemaLocation resolver works
> ----------------------------------------------------------------
>
>                 Key: DAFFODIL-2616
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2616
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Documentation, Website
>    Affects Versions: 3.2.1
>            Reporter: Mike Beckerle
>            Assignee: Mike Beckerle
>            Priority: Major
>             Fix For: 3.4.0
>
>
> We badly need an end-user doc/article on the daffodil.apache.org site that explains how Daffodil resolves include/import schemaLocations. 
> All our larger DFDL schemas are depending heavily on this behavior now. 
> The behavior of Daffodil's resolver is very sensible, reasonable, and predictable, which is why we're leaning on it so heavily now in large schemas. 
> Probably should also cover packaging schemas into Jars. 



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