I'm not sure how keys would help you here. My suggestion is to get rid
of the //vform and use either an absolute path, or a relative path
based on your current context...
using // makes the processor do a lot of work that it doesn't need to,
if you know where your vform elements are going to occur.
Josh
On Thu, 26 Aug 2004 15:44:35 -0500, Tengshe, Ashish
<tengshe(_dot_)ashish(_at_)principal(_dot_)com> wrote:
Ok, sorry about that, here is the category
<?xml version="1.0" encoding="UTF-8"?>
<Search>
<SearchResults>
<vform>
<item_id>BB55554</item_id><rvsn_id>1</rvsn_id><title_txt><![CDATA[RESOURCE
NEWSLETTER]]></title_txt></vform>
<vform>
<item_id>BB55552</item_id><rvsn_id>7</rvsn_id><title_txt><![CDATA[MAILER]]></title_txt><Category>General
Marketing</Category></vform>
<vform>
<item_id>BB5555CO</item_id><rvsn_id>0</rvsn_id><title_txt><![CDATA[INSTANT
ISSUE PAC]]></title_txt></vform>
<vform>
The output I want is a table with
item_id | title_txt | category // grouped by category
Should I use Keys instead?
Thanks,
Ashish D. Tengshe
IT System Analyst
Tengshe(_dot_)Ashish(_at_)Principal(_dot_)com
-----Original Message-----
From: Josh Canfield [mailto:joshcanfield(_at_)gmail(_dot_)com]
Sent: Thursday, August 26, 2004 2:14 PM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] XSL taking very long
The XML provided doesn't have a Category element...
You probably shouldn't be using //vform which translates to
/descendant-or-self::node()/child::vform and causes the entire node
tree to be searched for vform elements from the root to the deepest
leaf. Depending on your context you probably just need vform, or
perhaps /Search/SearchResults/vform.
Josh