[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
RE: [xsl] Optimal configuration of the XSLT processor
Subject: RE: [xsl] Optimal configuration of the XSLT processor From: "Michael Kay" <mhkay@xxxxxxxxxxxx> Date: Mon, 5 Mar 2001 13:42:40 -0000 |
In Saxon the most efficient approach here is to pre-build any source document that will be used as input to multiple transformations as a Saxon DocumentImpl object (or TinyDocumentImpl). It doesn't matter which of the three documents is the primary source and which are supplied as parameters. Mike Kay > -----Original Message----- > From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Shakeel > Mahate > Sent: 15 February 2001 00:07 > To: XSL-List@xxxxxxxxxxxxxxxxxxxxxx > Subject: [xsl] Optimal configuration of the XSLT processor > > > I need suggestions on optimal configuration of the XSLT processor for > my Java servlet web application. > > My transformation consists of the following components: > > "generic.xsl" > One stylesheet for the complete application > > "layout.xml" > Users will write a configuration file in XML. It contains the XML > tags representing the various HTML controls. The XML tags will have > the corresponding templates in the generic.xsl stylesheet > > "container.xml" > Container will represent the data which will be populated in the > HTML forms. In reality this is not a document, rather an > in-memory DOM > > "i18n.xml" > This XML document represents the labels specific to a locale. > > Now I have three inputs, one stylesheet. Not all the inputs > are files. > > My question is, how should I configure my Xalan 2.0.0 or Saxon XSLT in > my servlet. > > I know I can precompile my static stylesheet, since it is static. > > Which of the others can I make a source and which of them can be > parameters? > > Can in-memory DOM object become a parameter? > > Should DOM "container.xml" be a source? > > I will have one instance of the XSLT processor which I will > clone everytime > I have to transform the input, rather than create an instance > for every > request. This is a requirement since it XSLT processor are > single threaded > > Can you critic my architecture, provide suggestions. > > -Shakeel Mahate > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Re:, Chris Bayes | Thread | [xsl] translate (string, ''' ,, Samuzeau Pascal |
Re: [xsl] [exsl] EXSLT 1.0 - Common, Jeni Tennison | Date | RE: [xsl] FW: Coordination of <scri, Michael Kay |
Month |