Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] XML - XSLT own application

From: "Michael Kay" <michael.h.kay@--------.--->
To: <varun@---------.--->,<xml-dev@-----.---.--->
Date: 9/9/2004 11:32:00 AM
> 
> Is there some documentation I could find, as to how is an XSLT applied
> to an XML.
> 

A typical XSLT processor will have (a) a command line interface, and (b) an
API. Some also have a GUI front-end, or can be invoked via GUI toolsets such
as Stylus Studio and XMLSpy">XMLSpy.

For example, if your chosen XSLT processor is Saxon, you can invoke it from
the command line using a command such as

java -jar saxon8.jar source.xml stylesheet.xsl >output.html

or you can use the JAXP API, which is also supported by other Java-based
XSLT processors; or you can just select "Saxon" as your chosen processor in
Stylus Studio or XMLSpy">XMLSpy and press the right buttons.

If you want to do the transformation in a browser, you can invoke it
automatically by using an <?xml-stylesheet?> processing instruction on the
XML page and just loading the XML into an XSLT-aware browser, or you can
invoke it explicitly using a (typically JavaScript) API from script in your
HTML page.

The details depend on which XSLT processor you choose.

Michael Kay


transparent
Print
Mail
Like It
Disclaimer
.

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.

.
.

transparent

transparent