Page 1 of 1

resolving xsl:includes that are out of scope

Posted: Fri Nov 26, 2010 1:43 pm
by GraemeBryce
Hi

I have an XSLT "html.xslt" that makes use of a number of variables like $something that are in turn are defined in a file "includes.xslt".

I then have a file "default.xslt" that is used as the root of the transform at runtime. This file uses <xsl:include/> to add references to both of the earlier files. Of course all this works.

However when I am editing the html.xslt file, oxygen reports errors for all the lines that include variables as the definitions for them are out of scope.

I can not simply add an <xsl:include> into html.xslt and when I then run the default file the template from include are included twise and the transforms fail.

For more comple reasons I am also not able to remore the include from the default - there are many more parts to the system some of which do and some of which do not require certain scope.

Is there a way I can have Oxygen know that the includes.xslt files should be in scope during editing but without actually using and <xsl:include> node?

thanks

Re: resolving xsl:includes that are out of scope

Posted: Fri Nov 26, 2010 1:50 pm
by adrian
Hello,

You can find the solution to this included XSLT validation problem here:
http://www.oxygenxml.com/forum/post16872.html#p16872
I've just posted this yesterday.

Regards,
Adrian