Re: expand conditional variable in xsl:key match

I see.  Looks like my options are:
1. investigate forward-walk
2. enhance incoming data (the current design is to
keep process prior to XSLT generic with no business
logic, this will have to break that)

3. go back to Saxon6.0.2.  Somehow variable was
allowed in xsl:key match/use in that version, I had to
expand the variable out when I upgraded to Saxon6.5.2,
which is the cause of this problem I am having now.
When the variables are expanded out, the performance
went down drastically concurrently, which is another
reason I might decide to go back.
4. wait until WebLogic6.1 supports JDK1.4 and move up
to Saxon7.5.1 (this probably will never happen)

Since we might want to skip WebLogic7.1, we seems
committed to WebLogic6.1 for an extended period,
therefore option #3 might be the most viable at this
time for me.

Cheers,
Wendell

___&&__&_&___&_&__&&&__&_&__&__&&____&&_&___&__&_&&_____&__&__&&_____&_&&_
    "Thus I make my own use of the telegraph, without consulting
     the directors, like the sparrows, which I perceive use it
     extensively for a perch." -- Thoreau