Scott,
Checked out the fix and all seems to work just fine. I have
just two questions... for now..
Any estimate on the Sorted Iterator issue ?? I tested the SQL
code, it is still there. I have modified the Unit Tests in
samples/extensions/sql/streaming and will check them in.
I should also look into the bugzilla and submit my Unit Test
code.
The second question is related to the other problem with variable
testing. it seems that the root problem was that I am creating a
variable by possibly assigning it the same variable in a for-each
loop using a choose statement. Its not as complicated as it sounds,
see previous sample. Its all about the ability to mutate variables,
Xalan (DOM mode) allowed it. Now in a single instance, it is not
being allowed. The big questions is, are we closing all the loopholes
if so I have a bigger problem. If not should we make it work the same
for all cases ??
Regards
John G
[EMAIL PROTECTED] wrote:
> John Gentilin <[EMAIL PROTECTED]> wrote:
> > Better but still broken.
>
> OK, I've added some simple tests to the Bugzilla2925 test to test returns
> of a DTM, DTMIterator, and DTMAxisIterator. Fixed bug in OneStepIterator
> to set up the NodeTest to DTMFilter.SHOW_ALL. Ran the SQL sample, and it
> seems happy. Hopefully, all should be well now... try again.
>
> Sorry for the problems.
>
> -scott
