Re: TreeWalker lockup Xerces1.0.1-Java

[Ralf Pfeiffer <rp...@apache.org>]

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 something we're doing wrong but the nextNodemethod seems
> like it's not finding the end of the documentand just keeps looping
> back to the start of the doc. if you remove any of the <c> elements in
> lockup.xml then it allseems to work and nextNode correctly returns the
> <b> node. i'd like to know if anyone can see what we're doing wrong
> orif this might be a bug. usage of attached java program:   java Loop
> lockup.xml any help much appreciated, thanksgreg platform: windows
> 2000, jdk1.2.2, and *not* using hotspot.

Re: TreeWalker lockup Xerces1.0.1-Java

[Greg Matthews <gm...@flex.com.au>]

how do i get a copy of the "latest code" as opposed to
the downloadable 1.0.1 jar?

i also get the result that you get but when i try it
the code never exits back to the command prompt.

i tried putting a println in the acceptNode method
of the NodeFilter implementation to see what nodes
it was visiting and it seems to cycle through the
DOM tree in an infinite loop.

greg.

----- Original Message ----- 
From: Ralf Pfeiffer <rp...@apache.org>
To: <xe...@xml.apache.org>
Sent: Tuesday, February 01, 2000 11:47 AM
Subject: Re: TreeWalker lockup Xerces1.0.1-Java


> 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
> >
> > Greg Matthews wrote:
> >
> >> dear all, we have encountered a problem with using the treewalker.
> >> not sure if it's something we're doing wrong but the nextNodemethod
> >> seems like it's not finding the end of the documentand just keeps
> >> looping back to the start of the doc. if you remove any of the <c>
> >> elements in lockup.xml then it allseems to work and nextNode
> >> correctly returns the <b> node. i'd like to know if anyone can see
> >> what we're doing wrong orif this might be a bug. usage of attached
> >> java program:   java Loop lockup.xml any help much appreciated,
> >> thanksgreg platform: windows 2000, jdk1.2.2, and *not* using
> >> hotspot.
> >
> 

Re: TreeWalker lockup Xerces1.0.1-Java

[Ralf Pfeiffer <rp...@apache.org>]

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
>
> Greg Matthews wrote:
>
>> dear all, we have encountered a problem with using the treewalker.
>> not sure if it's something we're doing wrong but the nextNodemethod
>> seems like it's not finding the end of the documentand just keeps
>> looping back to the start of the doc. if you remove any of the <c>
>> elements in lockup.xml then it allseems to work and nextNode
>> correctly returns the <b> node. i'd like to know if anyone can see
>> what we're doing wrong orif this might be a bug. usage of attached
>> java program:   java Loop lockup.xml any help much appreciated,
>> thanksgreg platform: windows 2000, jdk1.2.2, and *not* using
>> hotspot.
>