RE: URIResolver

That's it. I was thinking that once I set the URIResolver, I was done.
Easy fix though. Thanks much. I guess .NET programmers and Java
programmers CAN get along. LOL.

Thanks again.

-Kevin


-----Original Message-----
From: Joe Fawcett [mailto:joefawcett@xxxxxxxxxxx]
Sent: Tuesday, September 20, 2005 1:49 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  URIResolver

I have very little experience of using Java for XML but in .NET you need
to pass the resolver twice, once when loading the XSLT to facilitate
xsl:include/import and once when transforming to resolve calls to
document(). the difference being that the former are resolved on loding,
the latter at the instant of transformation.
(There is also an issue with security, document() is not allowed by
default by untrusted callers, I don't know if this applies with xalan.)
Joe

----- Original Message -----
From: "Kevin L. Cobb" <kevin.cobb@xxxxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, September 20, 2005 6:22 PM
Subject:  URIResolver


This may be somewhat off topic for this list so I apoligize in advance.

I've implemented a URIResolver for my transformer calls. For some
reason, when I use the document('') XPATH expression function, the
URIResolver does not get called. Instread I get the error "(The system
cannot find the file specified)". What I've read says that document()
should use URIResolver. Perhaps it's the implenation I'm using?

      <xsl:for-each select="document('facility_map.xml')">
         <xsl:value-of select="key('facilityIDMap', $lookup)/@value"/>
      </xsl:for-each>

My Transformer Factory Implementation is:
org.apache.xalan.processor.TransformerFactoryImpl

-Kevin