Although I hate to say it, providing a full example that explicitly and
reproduceably shows the bug case is a big help in solving bugs like
this.  I'm not sure how scrubbing your file fits into your work
schedule; I'm also not sure exactly what point we're actually going to
get a definitive fix for this.  Unfortunately, a little bit of
uncertainty comes by default with most all-volunteer projects like
Apache.  8-)

(Oh: if you do post your files, you should attach them to a bugzilla
report, not send them to the list.  If you're pretty sure that this is
the same as an existing bug, add your info there; otherwise feel free
to open a new bug.  If we later find it's really the same bug we can
dup it, that's OK; we definitely appreciate it when users do their
homework like this!)

Not a fix but a workaround: is there any way you can break your file
into chunks and process the bits separately?   Or, can you break the
data up into several files, and then process one 'list' file that
simply points to the individual data files - you can then use
document(..) in the stylesheet to read each bit of data file in
separately, but in the same stylesheet.  I'm not sure, but loading the
same number of 'nodes' from different documents (rather than just one
document) might change the data enough to not trigger the bug.  I'd
like to say that using Xalan from the API rather than the command line
would help, but that's actually pretty unlikely; DTM issues are
fundamentally the same in both cases.

- Shane

=====
<eof aka="mailto:[EMAIL PROTECTED]";
 quote="A mirror is like a window on the other side of behind you."/>

__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com

Reply via email to