 |
|
|
Philip wrote:
> we have a very complex xsl stylesheet of 1200 lines or more and it seems
> like a good idea to seperate parts out into different xsl sheets that can be
> imported.
>
> The problem is that in the BODY onload event we run a procedure that moves
> data fields into their correct places ... and after we move one of the larger
> sections of xsl into a seperate sheet, it fails. The section that we want to
> move in fact creates the data fields based on metadata in the xml file.
BODY onload sounds like script (usually JavaScript, with IE/Win VBscript
is also possible) in a HTML document. Such a HTML document might be the
result of an XSLT transformation but I wonder how that relates to
using/importing stylesheet modules or not. Can you provide some more
details? Where does the XSLT transformation happen, on the server, or on
the client? Which XSLT processor do you use?
With the failure, do you get any error message?
--
Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
