Adam Jenkins schrieb:
Just so you know the complexity of the situation:
we have between 30 and 40 index xml files (changes daily). We are
only given the first one, which tells us two things:
1) where 20 data files are
2) where the next 'index' file is...that contains references to the
next 20
Adam Jenkins schrieb:
Try to avoid the temptation to force XSLT into using stateful
non-XSLT objects
Yep, understood, unfortunately the 'best practice' way of doing what I
need to do (large multi document xslt processing block) is just way
too memory intensive due to recursion requirements.
We
'll just double the ram on the
processing machine and go on with life :)
Unfortunately, delving into DTMDefaultBase.java is waaay beyond my
expertise ;)
Thanks for the suggestions
--- On Tue, 21/4/09, kesh...@us.ibm.com wrote:
From: kesh...@us.ibm.com
Subject: Re: odd NodeSet behavior
To
> The one big draw back of XSLT is crappy recursion.
There are ways for an XSLT processor to reduce recursion overhead --
recognizing opportunities to turn tail-recursion into iteration is a big
one -- but I don't think Xalan implements much along those lines yet. Good
opportunity for someone w
.com
Subject: Re: odd NodeSet behavior
To:
Cc: xalan-j-users@xml.apache.org
Received: Tuesday, 21 April, 2009, 10:51 AM
> Then, when I had to collect a range of different nodes to work with
> (kind of like a preprocessing step) I created one directly and added
> nodes to it. They added cor
> Then, when I had to collect a range of different nodes to work with
> (kind of like a preprocessing step) I created one directly and added
> nodes to it. They added correctly, however I can no longer use
> xsl:for-each.
> select="java:org.apache.xpath.NodeSet.new()"/>
A more idiomatic and mor
Adam Jenkins schrieb am 20.04.2009 um 14:46:55 (-0700):
>
> I have notice some really odd behavior when using
> org.apache.xpath.NodeSet.
> Then, when I had to collect a range of different nodes to work with
> (kind of like a preprocessing step) I created one directly and added
> nodes to it. Th
Hi All,
I have notice some really odd behavior when using org.apache.xpath.NodeSet.
I use it in two different ways. The first, is I have some custom extension
functions that return a NodeSet, that I can then loop over. They work fine.
Then, when I had to collect a range of different nodes t
