I've been using XSLT, period, for a long time, and I don't recall problems,
either. The thing is, this cropped up in a big way a few weeks ago, and I
know for a fact that as late as yesterday I had tests that broke.
However, today I reran some tests (Xalan command line), and of course
everything works. It works with Windows-style paths, UNIX-style paths,
absolute URLs, relative URL's, prepending the file: scheme, leaving it out,
etc etc. In fact, I can't make it break. :-)
I'm thinking that maybe we got bit by the dreaded Xerces+Xalan
version-out-of-sync problem, which normally we really pay a lot of attention
to. This is difficult to prove.
Regards,
Arved Sandstrom
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Lopez
Sent: Wednesday, February 14, 2001 4:43 AM
To: Orion-Interest
Subject: Re: Why xsl:include seems to try to find files in /Orion folder
andnotweb-app root?
Hi,
I've been using Xalan for quite a long time and whenever I used
<xsl:import href="fileName.xsl"/>, it always used the directory where
the xsl was located as base directory, NOT the the working directory.
This includes Xalan 1.2.x versions as I haven't upgraded to 2.0 yet. So
I would say Xalan follows the specificaction.
Regards,
Dan
Arved Sandstrom wrote:
>
> We have observed this behaviour with Xalan (1.2.x family) both in and
> outside of app servers. Xalan uses the "working directory", according to
> Java, as the base URI. Which is of course wrong.
>
> Dunno about Xalan2. Possibly fixed. In any case I'm planning to switch
over
> to Saxon.
>
> Regards,
> Arved Sandstrom
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Cramer
> Sent: Tuesday, February 13, 2001 4:54 AM
> To: Orion-Interest
> Subject: RE: Why xsl:include seems to try to find files in /Orion folder
> and not web-app root?
>
> Check out the XSLT spec at http://www.w3.org/TR/xslt#include. According to
> the spec, in an <xsl:include> tag, a relative URI as the value for the
href
> attribute should be interpreted as starting in the same directory as the
> including stylesheet.
>
> Example:
> assume that a stylesheet /www/xsl/A uses the tag: <xsl:include
href="B">,
> then the XSLT engine should include the stylesheet /www/xsl/B.
>
> If this isn't what you're seeing, then your processor has a bug.
>
> This might help more than my suggestion before :-)
> Dan Cramer
> Chief Architect
> Dynamic Resolve, LLC
> Internet Solutions Consulting
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Duffey, Kevin
> > Sent: Monday, February 12, 2001 5:47 PM
> > To: Orion-Interest
> > Subject: Why xsl:include seems to try to find files in /Orion folder and
> > not web-app root?
> >
> >
> > Hi,
> >
> > When I use the <xsl:include..> directive, it appears to look in
> > server root
> > dir, and not the web-app root its deployed in. I am not quite sure if
this
> > is something to do with Orion, or if all servers operate in this
> > manner and
> > therefore its an error of the XSLT technology. Or..perhaps its an error
of
> > the saxon library I am working with. Just wondering if anyone working
with
> > Orion and XSL have seen this problem or not?
> >
> > Thanks.
