Cart
|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: with-param looping problem...
 Basically, I'm trying to group the task with the job and the resource assigned to the task. The task UID seems to provide the common element to group them all together. For example, the Task/UID is referenced in the Assignemnt node as the TaskUID, which also includes the ResourceUID. I'm trying to use the //Assignment/ResourceUID to locate the //Resource/UID and retrieve the //Resource/Name. So, in the psuedo code that I wrote to get me started, I thought: <For each //Task> Select the Task Name Assign the UID to a param (or variable) called $rid Call a template that uses the $rid param (or variable) to retrieve the //Assignment/ResourceUID Write the //ResourceID to a param (or variable) called $name Pass the $name param (or variable) to another template to retrieve the //Resource/Name </for each> That's where I started...almost. I initially tried grouping these values with keys a la Muench, but I had no luck. Keeping the keys seemed to make sense because I could (or thought) Iretrieve the values without traversing the nodes over and over again. I was ecstatic with the stylesheet sample I sent, because I was at least able to retrieve some //Resource/Names. Anyway, I revised the code and took most of the oddities out. I'm still coming up empty on the // Resouce/Names. Does eliminating the <for each> and calling individual templates to process each node make more sense? Should - but I still can't seem to group these things together. ---- bob wilkins ---- 
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
