Hi Robert,
I'm not able to reproduce the problems that you describe, so I don't
know whether these problems were corrected by Santiago recently or by
somebody else. Have you tried using the latest code in CVS (or the latest
nightly build)? Do you have a test case that demonstrates this problem?
If you still see the problem using the latest code, please open a bug
report, with a complete, stand-alone test case.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:[EMAIL PROTECTED]
"Robert Koberg" <[EMAIL PROTECTED]>
2003-10-17 08:45 AM
Please respond to xalan-dev
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: Xalan Java 2.5.2
Hi,
There is another inconsistency between xalan and xsltc.
Overview:
According to most API's you can set a URIResolver on the
TransformerFactory
and one on the Transformer. Generally, the resolver set on the
TransformerFactory resolves xsl:includes and xsl:imports. If set on the
Tranformer it resolves document() function calls.
-----
The bug/inconsistency:
- standard xalan requires you to set a URIResolver on the
TransformerFactory
for xsl:include and xsl:import and set one on the Transformer for
document()
- xsltc xalan uses the TransformerFactory for both xsl:include/xsl:import
and document() -- you cannot set a resolver on the Transformer for
document(), like the standard xalan.
--
FYI:
- Saxon allows you to set a resolver on the TransformerFactory to resolve
both includes/imports and document().
It also lets you set one for the factory and one for the transformer. When
this is done the factory resolves include/import and the transformer
resolves document(). This is the best way, because, in IMHO, you get the
Transformer from the factory, so if you don't set one on the Transformer
it
defaults to the one set on the factory.
I would hope that both xalan and xsltc would follow Saxon's approach.
Best,
-Rob
