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/02 12:51:00 UTC

[jira] [Reopened] (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 reopened DAFFODIL-2616:
-------------------------------------

While verifying this ticket found the following difference between the javadoc and scaladoc pages.

From javadoc page:

The *EntityResolver* isn't thread safe, but it also is expensive and stateful, so we use ThreadLocal to only create one instance per thread.

 

From scaladoc page:

The *DFDLCatalogResolver* isn't thread safe, but it also is expensive and stateful, so we use ThreadLocal to only create one instance per thread.

> 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)