This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: import and include problems
- To: xsl-list at mulberrytech dot com
- Subject: RE: import and include problems
- From: "Scott Boag/CAM/Lotus" <Scott_Boag at lotus dot com>
- Date: Fri, 5 May 2000 12:41:36 -0400
- Reply-To: xsl-list at mulberrytech dot com
It should work fine in Xalan 1.0.1 also... it looks for imports and
includes relative to the including stylesheet. A common problem is that
people pass in a stream but don't set the system ID, so Xalan doesn't know
where the base directory is for the stream, so it defaults to the current
directory.
-scott
"Selva, Francis"
<Francis.Selva@purcha To: "'xsl-list@mulberrytech.com'" <xsl-list@mulberrytech.com>
sepro.com> cc: (bcc: Scott Boag/CAM/Lotus)
Sent by: Subject: RE: import and include problems
owner-xsl-list@mulber
rytech.com
05/05/2000 11:55 AM
Please respond to
xsl-list
I have never used Xalan but with Saxon xsl:import works fine.There is no
special environment settings for using this XSL element in Saxon.And
considering the usage of this element,I guess there will be no special
setting for using this element in any processor except that this element is
not supported in MSXSL.I guess someone in the list who is using Xalan may
throw some light for you.
Francis
> However, the Xalam parser always looked for the file from my
> root directory
> and gave me 'import file not found error'.
>
> I don't know what else I am missing or what environment
> variables I should
> set. Does anyone have this kind of problem before?
> I really appreciate your help!
> Ying
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list