Return-Path: Delivered-To: apmail-xml-xalan-j-users-archive@www.apache.org Received: (qmail 38534 invoked from network); 28 May 2004 17:38:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 28 May 2004 17:38:03 -0000 Received: (qmail 52261 invoked by uid 500); 28 May 2004 17:38:15 -0000 Delivered-To: apmail-xml-xalan-j-users-archive@xml.apache.org Received: (qmail 52098 invoked by uid 500); 28 May 2004 17:38:12 -0000 Mailing-List: contact xalan-j-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list xalan-j-users@xml.apache.org Received: (qmail 52035 invoked by uid 98); 28 May 2004 17:38:11 -0000 Received: from cebert@pocketthis.com by hermes.apache.org by uid 82 with qmail-scanner-1.20 (clamuko: 0.70. Clear:RC:0(130.94.5.242):. Processed in 1.279271 secs); 28 May 2004 17:38:11 -0000 X-Qmail-Scanner-Mail-From: cebert@pocketthis.com via hermes.apache.org X-Qmail-Scanner: 1.20 (Clear:RC:0(130.94.5.242):. Processed in 1.279271 secs) Received: from unknown (HELO exchange.pocketthis.com) (130.94.5.242) by hermes.apache.org with SMTP; 28 May 2004 17:38:08 -0000 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C444DA.29D73328" X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Subject: RE: URIResolver Date: Fri, 28 May 2004 10:35:26 -0700 Message-ID: <4E5B4E5784A39F4283BC4FA9A7F7A01BB95E1C@exchange.pocketthis.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: URIResolver Thread-Index: AcRD/pZ//sUGntsXRTKnNIxf49jTUwAJONVA From: "Christopher Ebert" To: X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------_=_NextPart_001_01C444DA.29D73328 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 Try setting the URIResolver on your factory before you generate the Transformer. =20 Chris -----Original Message----- From: Robert van Loenhout [mailto:r.vanloenhout@greenvalley.nl]=20 Sent: Thursday, May 27, 2004 08:26 To: xalan-j-users@xml.apache.org Subject: URIResolver =09 =09 =09 Hi! =20 I am using local xsl files to transform xml documents into html. I wanted to cache those xsl files, because they are used often in my application and usually stay the same. The xsl files also use xsl:import. =20 I looked in the API documentation and found the setURIResolver method for TransformerFactory and Transformer classes. So I made my own URIResolver and used them in the setURIResolver. =20 URI xsl =3D new File(xslFile).toURI(); Transformer transformer =3D tFactory.newTransformer(new StreamSource(xsl.toString())); CachingURIResolver resolver =3D new CachingURIResolver(); tFactory.setURIResolver(resolver); transformer.setURIResolver(resolver); ... transformer.transform(... =20 Unfortunately the resolve method of my CachingURIResolver is never called! The transformation is done normally. =20 I am using Xerces-j_2_6_2 and Xalan-j_2_6_0. =20 How can I get this to work correctly? Or is there an easier way to accomplish my goals? =20 Thanks for any help. Robert. =09 =09 =09 =09 =09 =09 =09 =20 =09 ------_=_NextPart_001_01C444DA.29D73328 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
 
    Try setting the URIResolver on your factory = before you=20 generate the Transformer.
 
Chris
-----Original Message-----
From: = Robert van=20 Loenhout [mailto:r.vanloenhout@greenvalley.nl]
Sent: = Thursday, May=20 27, 2004 08:26
To: = xalan-j-users@xml.apache.org
Subject:=20 URIResolver

Hi!
 
I am using local xsl files to transform xml documents into = html.
I=20 wanted to cache those xsl files, because they are
used often in my=20 application and usually stay the same.
The xsl files also use=20 xsl:import.
 
I looked in the API documentation and found the setURIResolver = method=20 for
TransformerFactory and Transformer classes. So I made my own=20 URIResolver and
used them in the setURIResolver.
 
  URI xsl =3D new File(xslFile).toURI();
  = Transformer=20 transformer =3D tFactory.newTransformer(new=20 StreamSource(xsl.toString()));
  CachingURIResolver resolver = =3D new=20 CachingURIResolver();
  = tFactory.setURIResolver(resolver);
 =20 transformer.setURIResolver(resolver);
  ...
 =20 transformer.transform(...
 
Unfortunately the resolve method of my CachingURIResolver is = never=20 called!
The transformation is done normally.
 
I am using Xerces-j_2_6_2 and Xalan-j_2_6_0.
 
How can I get this to work correctly? Or is there an easier way = to=20 accomplish my goals?
 
Thanks for any help.
Robert.
                                                                         =
    =20
                                                                         =
    =20
                                                                         =
     =20
                                                                         =
  =20

               =20
                                                                =20
=00 ------_=_NextPart_001_01C444DA.29D73328--