LOTS of Tidy Failures?

We're getting a lot of these in our error.log:

The following error occurred: null
java.lang.NullPointerException
at org.w3c.tidy.Clean.textAlign(Unknown Source)
at org.w3c.tidy.Clean.blockStyle(Unknown Source)
at org.w3c.tidy.Clean.cleanNode(Unknown Source)
at org.w3c.tidy.Clean.createStyleProperties(Unknown Source)
at org.w3c.tidy.Clean.createStyleProperties(Unknown Source)
at org.w3c.tidy.Clean.createStyleProperties(Unknown Source)
at org.w3c.tidy.Clean.createStyleProperties(Unknown Source)
at org.w3c.tidy.Clean.cleanTree(Unknown Source)
at org.w3c.tidy.Tidy.parse(Unknown Source)
at com.screenscraper.util.General.tidyHTML(General.java:1618)
at com.screenscraper.scraper.ScrapeableFile.scrapeData(ScrapeableFile.java:3593)
at com.screenscraper.scraper.ScrapeableFile.scrape(ScrapeableFile.java:2126)
at com.screenscraper.scraper.ScrapingSession.scrapeFile(ScrapingSession.java:2262)
at com.screenscraper.scraper.Scraper.scrape(Scraper.java:200)
at com.screenscraper.scraper.Scraper.run(Scraper.java:110)

Running 3.0, nothing strange showing up in the scrape logs. Not seeing the "tidying failed" messages you occasionally see, either.

LOTS of Tidy Failures?

Oop! Thanks for spotting that. Looks like one of our debug parameters inadvertently slipped in. That would affect anyone using the SOAP interface, which I'm guessing you're doing. That will be fixed in the next alpha version.

Todd

LOTS of Tidy Failures?

We were having some stability issues, and just for fun we did the upgrade to 18a in our QA environment. I think that fixed it.

Curious: Why do I end up with this directory:

D:\home\brent\screenscraper\lws\webapps\axis\WEB-INF\attachments

Nothing in it. But I see it on any box with ss installed, I think.

LOTS of Tidy Failures?

Hi,

If I recall correctly, we made a fix for this in one of the more recent alpha versions. It's tricky, because it occurs outside of screen-scraper's code base, but I believe we were able to find a workaround. Would you mind upgrading one of your screen-scraper instances to the latest alpha, and seeing if the error still occurs?

Thanks much,

Todd Wilson