[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Nested Grouping problem

Subject: Nested Grouping problem
From: "Alex Aguilar" <alex@xxxxxxxxxxxx>
Date: Wed, 29 Nov 2000 02:07:58 -0800
java code nested grouping
This is a grouping problem. In fact its a nested grouping problem.

I've gone through your Jennison's helpful article on the Muenchian key
technique and searched through the newsgroup messages and the XSLT FAQ but
haven't found anything similar.

>From a flat XML structure like:

<FundList>
<Fund rowid="1">
    <fundName>Sarah's MoneyMarket Fund</fundName>
    <assetClass>MoneyMarket</assetClass>
    <capitalization/>
    <id>12845</id>
    <percent>0</percent>
    <risk>4</risk>
</Fund>
<Fund rowid="2">
    <fundName>Will's Fund</fundName>
    <allocCategory>Domestic Equity</allocCategory>
    <assetClass>Growth</assetClass>
    <capitalization>Small Cap</capitalization>
    <id>12345</id>
    <percent>0</percent>
    <risk>4</risk>
</Fund>
<Fund rowid="6">
    <fundName>Alex's Fund</fundName>
    <allocCategory>Domestic Equity</allocCategory>
    <assetClass>Aggressive Growth</assetClass>
    <capitalization>Medium Cap</capitalization>
    <id>17378</id>
    <percent>0</percent>
    <risk>5</risk>
</Fund>
</FundList>


I want to create a nice looking page that looks like this.   I used to have
it working in XSL but then we found out there wasn't an easy way to get the
database to return a nice hierarchical XML like the one I had designed ;-(

My problem is I'm relatively new to XSL and am not sure as to the best way
to go about creating keys to accommodate four levels of nested grouping. As
I stated XML cannot be modified. It has to be processed in this flat format.
I'm able to get up to one level but once I start nesting for-each loops
inside each other I don't get the desired results.

I was thinking of perhaps hardcoding the four top level categories (Cash,
Domestic Fixed, Domestic Equity and International Equity). The only thing I
don't like about that is that if ever another allocation category were added
then someone has to make a change to the XSL.  Is there a way to perhaps a
make a robust XSL so that no matter how many categories are added the XSL
would still handle it?

To be honest, I'm kind of tired of spinning my wheels on this one and am
willing to monetarily compensate someone to help me solve this one.

Here are some reference files:

  FundList.xml - file containing the current flat XML structure
  FundList.xsl - my feeble attempt
  FundList.xls - an Excel file outlining the category structure

If anyone is interested in my offer, please contact me off the list at
alex@xxxxxxxxxxxx

thanks,
Alex Aguilar



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.