Subject: Re: [xsl] expand conditional variable in xsl:key match From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Wed, 18 Jun 2003 12:34:35 -0400 |
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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] expand conditional variab, Xiaocun Xu | Thread | Re: [xsl] expand conditional variab, Xiaocun Xu |
[xsl] Cannot use result tree fragme, abbouh | Date | Re: [xsl] Cannot use result tree fr, David Carlisle |
Month |