Subject: RE: [xsl] Using keys to filter nodesets From: "Amuchastegui, Maria" <Maria.Amuchastegui@xxxxxxxxxxx> Date: Wed, 21 Jan 2004 10:18:18 -0500 |
I was able to get it to work by using a variable to pass the value of the SubscriptionID and inserting a string function within the key function. Why didn't it work without the string function? - Maria <xsl:key name="MappingKey" match="Subscription/WDBillerID" use="../SubscriptionID"/> <xsl:variable name="SubID" select="/PresentationData/PageSpecific/SubscriptionList/Subscription/Subscri ptionID[1]" /> <xsl:template match="Biller"> <option> <xsl:attribute name="value"><xsl:value-of select="MappedBillerID"/></xsl:attribute> <xsl:value-of select="MappedBillerName"/> </option> </xsl:template> <xsl:apply-templates select="//Biller[WDBillerID = key('MappingKey', string($SubID))]"/> -----Original Message----- From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Wendell Piez Sent: January 20, 2004 4:46 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: Re: [xsl] Using keys to filter nodesets Hi Maria, One reason your filter isn't working may be if the XPath /PresentationData/PageSpecific/SubscriptionList/Subscription/SubscriptionID[ 1] returns every SubscriptionID in the document (the predicate [1] ensures, here, only that the SubscriptionID is the first child of its parent; maybe this is true of all of them. Passing a node-set as the second argument of key() returns all the nodes matching the key with values in that node-set.) If the intent of your template match is to match only that Biller whose WDBillerID is the same one (same node, not just same value) returned from the key using the value of the first SubscriptionID in the document, you could try match="Biller[generate-id(WDBillerID) = generate-id(key('MappingKey',/descendant::SubscriptionID[1]))]" If that isn't your intent, you may want to clarify what exactly you're trying to filter and how, with a sample of the source data we could look at. Cheers, Wendell At 04:05 PM 1/20/2004, you wrote: >I am trying to use a key to filter a nodeset. The individual elements work, >but when I put them all together the nodeset does not get filtered. What am >I doing wrong? - Maria > > ><xsl:key name="MappingKey" >match="/PresentationData/PageSpecific/SubscriptionList/Subscription/WDBille r >ID" use="../SubscriptionID"/> > > ><xsl:template match="//Biller[WDBillerID = key('MappingKey', >/PresentationData/PageSpecific/SubscriptionList/Subscription/SubscriptionID [ >1])]"> > <option> > <xsl:attribute name="value"><xsl:value-of >select="MappedBillerID"/></xsl:attribute> > <xsl:value-of select="MappedBillerName"/> > </option> ></xsl:template> ====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ====================================================================== 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] Using keys to filter node, Wendell Piez | Thread | [xsl] JScript embedded in xsl, annirack |
[xsl] Sorting Issue, SHEIKH Sajjad | Date | [xsl] Average result out of scope t, Fran |
Month |