[
https://issues.apache.org/jira/browse/DAFFODIL-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence resolved DAFFODIL-2616.
--------------------------------------
Resolution: Fixed
Fixed in commit 4f84e0472ca11390af2401a60d0c54ab9603db2f as part of
DAFFODIL-2739.
Documentation is available in java/Scala docs in DaffodilXMLEntityResolver
> 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)
