OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Coordinated XSL and XML inclusions?

[ Lists Home | Date Index | Thread Index ]

James Adams wrote:

> I have been trying for some time now to rewrite the bulk of a web
> application framework using XML and XSLT.  Essentially, the framework
> outputs an XHTML document by recursively parsing Java objects that can
> render themselves via a method call.  Each web application that uses
> the framework has a Site object that generates something like
> (excluding doctype and attributes):

> What I am trying to do is replace this templating nonsense with XML
> documents that represent a Site, Module, and View object
> respectively.  I have been using the XSL document() function from
> XPath to pull in the Module.xml document, which does the same to pull
> in the View.xml document.  This is fine, and it builds the result tree
> into an XHTML document as expected, but using this method I have to
> put the XSL parsing instructions for every one of my parsable XML
> files into one huge XSL document.  What I would much prefer to do is
> specify a separate XSL document for each XML document, and use the
> matched XSL to parse the XML and pull the resulting parsed document
> into the original source document.  Is there any way to do this?  I
> have been up to my eyeballs in standards documents for the past few
> weeks and have not been able to find an answer.  Any help would be
> greatly appreciated.

u do not *have* to place all your xsl into one huge xslt

why not bring in each seperate XSLT using xsl:include?

then use modes to disambiguate between matching 'xsl:template' templates.

gl, Jim Fuller


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS