Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0.x
-
Fix Version/s: None
-
Component/s: Xalan
-
Security Level: No security risk; visible to anyone (Ordinary problems in Xalan projects. Anybody can view the issue.)
-
Labels:None
Description
In case an XSLT file contains reference to any entities, and an entity resolver is used, the resolver is given a chance to look up in the catalog only after the original reference in the internet is consulted and fetched. A case may look like this:
<?xml version="1.0" standalone="yes" ?>
<!DOCTYPE transform [
<!ENTITY % w3centities-f PUBLIC "-//W3C//ENTITIES Combined Set//EN//XML"
"http://www.w3.org/2003/entities/2007/w3centities-f.ent">
%w3centities-f;
]>
<xsl:transform version="1.0"
...
For that case if no internet connection is available, a java.net.UnknownHostException is thrown by Xalan-J command line utility referencing "www.w3.org".
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
A new set of patches (in "diff -u" format) the resolve the issue, probably partially. In particular, XSLTC is likely to need extra attention.
An entity resolver, if available, is supplied to the transformer factory as an attribute, to be further provided for the reader instances.
An extra property is defined for this new sort of attribute.
A patched binary build is available form my blog page "XSLT, entities, Java, Xalan..." at http://s-n-ushakov.blogspot.com/2011/09/xslt-entities-java-xalan.html .
A patch the resolves the issue, probably partially. In particular, XSLTC is likely to need extra attention.
An entity resolver, if available, is supplied to the transformer factory as an attribute, to be further provided for the reader instances.
An extra property is defined for this new sort of attribute.