[
https://issues.apache.org/jira/browse/DOXIA-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed DOXIA-669.
--------------------------------
Resolution: Fixed
Fixed with
[3b1499d0572718fa4dcb7c6b775bedbe757d46c5|https://gitbox.apache.org/repos/asf?p=maven-doxia.git;a=commit;h=3b1499d0572718fa4dcb7c6b775bedbe757d46c5].
> Improve/rework CachedFileEntityResolver
> ---------------------------------------
>
> Key: DOXIA-669
> URL: https://issues.apache.org/jira/browse/DOXIA-669
> Project: Maven Doxia
> Issue Type: Improvement
> Affects Versions: 2.0.0-M3
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 2.0.0-M4
>
>
> While working on a few other the following flaws have been detected with the
> {{CachedFileEntityResolver}} which need to be addressed:
> * If a resource is not available, but through HTTP and the target will
> redirect to HTTPS {{HttpURLConnection}} will not follow by default and even
> worse it will not notify us
> * Our required resources: fml.xsd, xdoc.xsd and xml.xsd are only checked by
> system id and not public id which means you need to take care of multiple URLs
> * It perfoms outbound connections for resources which could be available
> offline, e.g., schemas from above
> * It logs zero information what is happening making debugging very hard
> * If a document does not supply a schema or DTD the validation fails while
> logically there is nothing to validate. E.g., HTML5 is now schemaless with
> mere {{<!DOCTYPE html>}}.
> Things to be done:
> * Have all supported schema in the classpath for fast access
> * Remove all not used schemas
> * Provide a public id to classpath resource mapping to avoid alternating
> system ids
> * Add debug logging to assist analysis
> * Don't fail if a schema is not provided
> * If URL is a file load directly because file IO is fast.
> Likely other points.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
