Re: [xsl] stylesheet organisation

[George Cristian Bina <george@xxxxxxxxxxxxx>]

It is not only the validation that fails... if the tool will normally 
offer you editing help by looking into the stylesheets for defined 
templates, variables, functions, etc. then you will loose that as well.

oXygen supports this though validation scenarios where you can define 
the main (entry point) stylesheet to be used instead of the one you edit.

One possibility to overcome this (if there is no support in the tool) is 
to define the referred components at the top of the stylesheet with an 
empty value or generating an error message that there is no proper 
definition for that component and reply on the import precedence to 
bring in the actual definition from the importing stylesheets - but this 
may hide errors when the module is imported from another stylesheet that 
does not define all the components, or it will delay their detection 
until runtime.

Best Regards,
George
--
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 9/2/11 5:08 PM, Tom T wrote:
> Ah yes, then I still get those error messages but just choose to ignore them, I don't find them useful in the debugging process anyway.
>
> ----------------------------------------
> > Date: Fri, 2 Sep 2011 14:55:48 +0100
> > From: andrew.j.welch@xxxxxxxxx
> > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: Re: [xsl] stylesheet organisation
> >
> > > They are imported once in each entry level stylesheet, this ensures they will only ever be imported once, - not sure what you mean by 'rely on tools to be aware of that'?
> >
> > If you have 3 stylesheets, 'a', 'b' and 'c'.
> >
> > If a imports both b and c, then you can refer to things in b from c,
> > however your editor would complain about the missing things unless it
> > knows about the entry point a.
> >
> >
> >
> > --
> > Andrew Welch
> > http://andrewjwelch.com