des
it was visiting and it seems to cycle through the
DOM tree in an infinite loop.
greg.
- Original Message -
From: Ralf Pfeiffer <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 01, 2000 11:47 AM
Subject: Re: TreeWalker lockup Xerces1.0.1-Java
> I als
I also don't get the behaviour you are describing with JDK1.2.2.
Ralf Pfeiffer wrote:
> Greg,
> I tried your example on Xerces1.0.1-Java and the latest code, and
> could not reproduce it. My output is:
> .! [b: null]
> .
>
> which is what I expect. I'll try it on JDK1.2.2, ASAP.
>
> -rip
>
> Gre
Greg,
I tried your example on Xerces1.0.1-Java and the latest code, and could
not reproduce it. My output is:
.! [b: null]
.
which is what I expect. I'll try it on JDK1.2.2, ASAP.
-rip
Greg Matthews wrote:
dear
all, we have encountered
a problem with using the treewalker. not
sure if it's somet
dear all,
we have encountered a problem with using the
treewalker.
not sure if it's something we're doing wrong but
the nextNode
method seems like it's not finding the end of the
document
and just keeps looping back to the start of the
doc.
if you remove any of the elements in
locku
