this example works WITHOUT Xalan in classpath
your example not worked in any my configuration, but then add one more
line....
1) then java.endorsed.dirs not set - it is using crimson or something like
from jre
2) i show packages and test this example on
a) internal j2re1.4.2_02 parser (i don't know which one there)
b) xalan 2.5.0 + correspond xerces (java.endorsed.dirs was set and
custom classloader was written)
c) xalan 2.6.0 + xerces (...)
Templates temp = tf.newTemplates(new StreamSource(args[0]));
Transformer t = temp.newTransformer();
// code change there
t.setURIResolver(new Resolver());
t.transform(new StreamSource(args[1]), new StreamResult(System.out));
near transformer URIResolver must be set.
all works fine on all tested solutions
- but it is doesn't work with xalan-2.5.0 in the web server (other jre
different from 1.4.2_02 i think it is reason)
and on the server with xalan 2.6.0 all works fine!
conclusion:
problem with old jre and xalan 2.5.0
ps i think this example must work without resolver for transformer, but this
problem is not so strong
pps i am ready to add this bug in bugzilla if you are sure
----- Original Message -----
From: "Henry Zongaro" <zongaro@xxxxxxxxxx>
To: "Vladimir I." <vi@xxxxxxxx>
Cc: <xalan-j-users@xxxxxxxxxxxxxx>
Sent: Tuesday, July 27, 2004 12:42 AM
Subject: Re: Xalan 2.5.0 & 2.6.0 document function fails.
> Hi, Vladimir,
>
> "Vladimir I." <vi@xxxxxxxx> wrote on 07/19/2004 03:48:34 AM:
> > > "Vladimir I." <vi@xxxxxxxx> wrote on 07/14/2004 03:36:24 AM:
> > > > trouble:
> > > > when i make transformation using Templates object document()
> function
> > > will
> > > > not call my custom URIResolver object
> > > > ex:
> > > > <xsl:include href="/BR/convert.xslt"/>
> > > >
> > > > <xsl:include href="/BR/price.xslt"/>
> > >
> > > This looks like a bug in Xalan-Java's implementations of the
> > > Templates interface. Both the interpretive processor and the
> compiling
> > > processor fail to pass the URIResolver from a TransformerFactory to a
> > > Transformer if the Transformer was created from a Templates object.
> > >
> > > Could I ask you to open a bug report in Bugzilla for this
> problem?
> > it was a bug in 2.5.0
> > when i try this in 2.6.0 - all fine (i was mistaked in previous letter)
> > it is still need to open a bug report ?
>
> I can't explain why you don't see this problem with Xalan-J 2.6.0; I
> see it with both the interpretive processor and with XSLTC.
>
> Try invoking the following example using this command-line:
>
> $ java Resolver dxxxxx.xsl dxxxxx.xml
>
> The Resolver.resolve method should be invoked four times, but I only see
> four calls.
>
>
>
>
> Thanks,
>
> Henry
> ------------------------------------------------------------------
> Henry Zongaro Xalan development
> IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
> mailto:zongaro@xxxxxxxxxx
>
Resolver.java
Description: Binary data
|
