It ist one, which uses URI, actually 7.6.

 

K.Rucker

 

-----Ursprüngliche Nachricht-----
Von: Michael Kay [mailto:mhk@mhk.me.uk]
Gesendet: Freitag, 13. Februar 2004 16:30
An: saxon-help@lists.sourceforge.net
Betreff: RE: [saxon] reading transformations from jar

 

Generally the policy in Saxon is to delegate all URI handling to Java.

 

You don't say which Saxon version you are using. Older versions use the java.net.URL class, newer versions use java.net.URI.

 

Michael Kay

-----Original Message-----
From: saxon-help-admin@lists.sourceforge.net [mailto:saxon-help-admin@lists.sourceforge.net] On Behalf Of Rucker, Karsten
Sent:
13 February 2004 10:46
To: saxon-help@lists.sourceforge.net
Subject: [saxon] reading transformations from jar

Hello,

 

I'm trying to read my xsl transformations from a jar file that is by creating a StreamSource with
a system_id argument starting something like "jar:file:/E:/xx...". This does work. But if
the transformation xsl:includes some other transformation by specifying a relative path the

Load fails.

Looking  closer into the source code, I found that usage of URI::resolve(relative path) in StandardURIResolver
just returns the relative path unchanged, if it has been constructed with a path, which starts with "jar:file:/...".

I do not know whether what I tried is supposed to work, but I found that it actually did work, when using the JDK1.4.2
included xalan. So I found the effect worth mentioning.

 

Best regards