[
https://issues.apache.org/jira/browse/XALANC-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776848#comment-13776848
]
Steven J. Hathaway commented on XALANC-745:
-------------------------------------------
The underlying Xerces-C has support for user-defined catalogs.
The Xalan-C library has linkages to support Xerces-C capability.
There is no work to my knowledge of creating a default catalog
(entity resolver) that will solve the problem.
The default (entity resolver) relies on the local file system
to acquire system resources and DNS to acquire remote resources.
- Steven J. Hathaway
> XalanExe unable to do transform on W3C doc types without workaround
> -------------------------------------------------------------------
>
> Key: XALANC-745
> URL: https://issues.apache.org/jira/browse/XALANC-745
> Project: XalanC
> Issue Type: Bug
> Components: XalanC
> Affects Versions: 1.10, 1.11
> Environment: Issue reproduced on Debian GNU/Linux and Windows XP
> using 1.10 and 1.11 binaries.
> Reporter: Bill Blough
> Assignee: Steven J. Hathaway
>
> Forwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702225
> Since W3C has started blocking some fetches of their documents due to
> overuse, it is no longer possible to transform xhtml (or presumably other W3C
> doc types) using XalanExe as shipped.
> If the source document is edited and the DOCTYPE URL is adjusted to reflect
> an existing local or non-W3C-hosted copy of the DTD, then the transform
> completes as expected.
> I suggest adding functionality to XalanExe that will allow it to make use of
> locally installed DTD/XSD catalogs instead of fetching docs from the W3C
> website.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
