logInfo not working in API
This seems to be something from the very latest alpha (5.0.22a). When I run my scrape that uses an outside JAR file, I get the following error:
An error occurred while processing the script: Kia - CSV
The error message was: NoSuchMethodError (line 20): com.screenscraper.scraper.ScrapingSession.logInfo(Ljava/lang/String;)V-- Method Invocation geocoder.geocode
The error message was: NoSuchMethodError (line 20): com.screenscraper.scraper.ScrapingSession.logInfo(Ljava/lang/String;)V-- Method Invocation geocoder.geocode
The JAR file does call
session.logInfo(), so perhaps it's not in the API anymore? Do I need to change my code?
I changed the logging to be
I changed the logging to be able to accept an Object as a parameter as opposed to a String, then it calls String.valueOf on those objects to log them. Unfortunately I forgot that for java libraries compiled before this change the method signatures then wouldn't match up. I added the old methods logging methods back in also so the next alpha release(5.0.24a) should resolve the problem. The other solution would be to recompile your libraries with a reference to the updated screen-scraper.jar.
Recompiling the code worked,
Recompiling the code worked, thank you.
logInfo update
Sorry this was an error in the last alpha release. We just put out a new update that should resolve the issue.
Sorry, I didn't see this till
Sorry, I didn't see this till I had already committed that last comment. I tried with 5.0.23a but still got the same error. Is there a newer version?
Chris, I can't seem to
Chris, I can't seem to duplicate this here. Is there another test case you can send me so I can see this issue? I'd love to fix it!
logInfo throws an exception
Hey,
this might be due to the changes that logInfo is throwing an exception if this action is not allowed. So if you add a try-catch-block around the call you should be good.
Edgar
I'm sorry, I don't quite
I'm sorry, I don't quite understand. What action is not allowed? Can I still use the logInfo command in my included library, I just have to catch exceptions? That's not really what this error indicates.