Subject: RE: [xsl] keys vs. parameters From: "Hunsberger, Peter" <Peter.Hunsberger@xxxxxxxxxx> Date: Fri, 7 Jun 2002 17:03:54 -0500 |
> You don't generate anything -- that's the responsibility of the processor. > Most implementations will "index" on an as-needed basis, so if you don't > refer to a key, there won't be any overhead. Since the key() function can > only return nodes in the same document as the context node, a processor is > required to keep information separate for each source document. Again, > with most implementations, that means only the documents for which there is > a call of the key() function will be "indexed". > > Both Xalan-J and Xalan-C++ implement keys this way. Ok, perhaps I'm missing something. I tried this with Xalan-J and in the context of a result set returned from an extension. I couldn't get the key to work. It was a pretty straight forward "match" and "using" (I've had far worse, including one I think I'm going to end up creating a question about come Monday) so I don't think I coded it wrong, but I'll try again... XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] keys vs. parameters, David N Bertoni/Camb | Thread | Re: [xsl] keys vs. parameters, Jeni Tennison |
Re: [xsl] Borders on column groups, David Carlisle | Date | RE: [xsl] keys vs. parameters, Hunsberger, Peter |
Month |