DO NOT REPLY [Bug 23470] - extension function fail if it's inside another extension element with xsl variable

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23470>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23470

extension function fail if it's inside another extension element with xsl variable





------- Additional Comments From joannet@ca.ibm.com  2003-09-29 14:49 -------
I couldn't duplicate this error.  I got the following output:

<?xml version="1.0" encoding="UTF-8"?>
output of xyz:element abc
output of xyz:function abc
output of xyz:element/xyz:function abc
output of xyz:element/xyz:function with xsl:variable abc
output of xyz:element xyz
output of xyz:function xyz
output of xyz:element/xyz:function xyz
output of xyz:element/xyz:function with xsl:variable xyz

Can you please attach an environment report.

2.5.1 - different behavior between xalan and xsltc - uri resolution

[Robert Koberg <ro...@koberg.com>]

Hi,

I am noticing that there is different behavior between the standard xalan
(org.apache.xalan.processor.TransformerFactoryImpl) and the xsltc
implementation (org.apache.xalan.xsltc.trax.TransformerFactoryImpl) when it
comes to resolving requests using the document() function.

In the standard xalan the resolver that resolves document() calls needs to
be set on the Transformer rather than the TransformerFactory. However, XSLTC
uses the resolver set on the TransformerFactory rather the Transformer when
resolving document() calls.

I would expect xsltc's behavior to be the same as the standard xalan impl.

Bug?
-Rob