Re: HTMLParserFactory.setParserWarningsEnabled(false) doesn't work.

You say that as if it's a good thing.
 
 - Neko's "forgiveness" comes from doing less.  You can't (in my
experience) use XPATH with it, for example.
 
 - The purpose of HttpUnit is to test for correct operation of websites.
If the HTML is not well-formed, the "proper" interpretation of that HTML
is indeterminate.  It may well be "good enough" if you're targeting a
particular browser, rather than targeting the W3C standards, of course,
but if that's your goal, you might be better off testing with a tool
like WATIR.

	-----Original Message-----
	From: [email protected]
[mailto:[email protected]] On Behalf Of
Harry Soehalim
	Sent: Wednesday, July 05, 2006 2:28 PM
	To: Discussion of use and development of HttpUnit
	Subject: Re:
[Httpunit-develop]HTMLParserFactory.setParserWarningsEnabled(false)
doesn't work.
	
	
	yeah, that's exactly what I actually ended up doing. Neko parser
is more forgiving than Tidy :-)
	
	Harry
	
	
	On 7/5/06, [email protected] <
[email protected] <mailto:[email protected]>
> wrote: 

		If your HTML is not well-formed, you may do better to
use the Neko parser rather than Tidy.  Or you could clean up the HTML
until it validates.
		 
		See http://www.w3.org/People/Raggett/tidy/  and
http://validator.w3.org/
		

			-----Original Message-----
			From:
[email protected]
[mailto:[email protected]] On Behalf Of
Harry Soehalim
			Sent: Monday, July 03, 2006 7:56 PM
			To: [email protected]
			Subject:
[Httpunit-develop]HTMLParserFactory.setParserWarningsEnabled(false)
doesn't work.
			
			
			Hello,
			
			I'm currently using httpunit v1.6.2. I came
across this standard error message:
			
			line 9,148 column 1 - Error: <js_popup_rnsurvey>
is not recognized!
			This document has errors that must be fixed
before
			using HTML Tidy to generate a tidied up version.
			
			which after some digging turn out to be from
Tidy.jar
			
			I have used httpunit ver1.5.2 and just upgraded
to ver1.6.2 recently. I didn't see this error message with ver1.5.2.
			
			Searching at mailing list for any solution to
turn off this error message, someone point out
HTMLParserFactory.setParserWarningsEnabled(), but it doesn't work. I'm
still getting the error message. Doesn't anybody other solution?

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

_______________________________________________
Httpunit-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/httpunit-develop