Re: [Htmlparser-developer] testStringBeanListener() consistently failing

[Derrick O. <Der...@ro...>]

Hi back,

Sorry, I've just been lurking the HTMLParser project lately. That's 
because I liked the open source experience I had with HTMLParser so much 
I started my own project:
    http://sourceforge.net/projects/connector/

I think the problem (although I didn't experience it) with 
testStringBeanListener() is the fetch of the external URL (slashdot.org) 
may fail and then the contents of the bean's string property won't 
change meaning the listener isn't fired (my guess is you were not 
getting data back from slashdot.org consistently and then not at all for 
a period, it should be back to OK now).

So I switched to a http://htmlparser.sourceforge.org/test/example.html, 
which is something I said I was going to do a long time ago anyway.

The change to a local string instead of a web page for the serialization 
test may have missed the point, since the intent is to be able to 
recover the connection and parse it after rehydration, so I switched it 
back to a URL (the same as above). I hope that's OK, it should go faster 
anyway because the page is smaller.  If it's not, we'll have to 
investigate why it isn't.

Derrick

Somik Raha wrote:

>Hi Derrick,
>  As of the last release, I'd noticed something
>peculiar - testStringBeanListener() would fail every
>once in a while. I ignored it, but then, after
>Kaarle's fix to the attribute bug today, I find that
>testStringBeanListener() fails every time.
>
>  I am not sure if we caused something to break
>(probably one of us did). Could you take a look when
>you are free ? Bytway, I did modify a few of the
>tests, and the part which requires a parser to hold a
>url to be serializable (I didn't actually understand
>why that was necessary). Could that have caused the
>problem ?
>
>Regards,
>Somik
>
>
>  
>