Chain Stanford Parser's exceptions up to Thrift so that the exceptions Thrift throws are the ones thrown by Stanford Parser

[dmnapolitano]

See http://stackoverflow.com/questions/15029424/apache-thrift-throwing-the-exception-thrown-by-the-code-executed-in-the-method

Basically, when any of the CoreNLP tools throw an exception, this exception should be thrown by Thrift to the client so that the client (user) can make an assessment about what to do with it. These exceptions provide a lot of utility, especially ones like "Your sentence is too long" or "Your sentence is somehow invalid."

[dmnapolitano]

log4j is certainly catching the exceptions...can we use log4j to return them to the client, somehow? I'm completely unfamiliar with this thing... :confused: