Issue #97 has been updated by Jonathan Clarke. Status changed from Assigned to Feedback Target version set to 1.1.1
Thanks for this, Rapha?l. I have committed it to trunk, and 1.1 branch. Should be released in 1.1.1. You can test using the nightly SNAPSHOT on 1.1 branch tomorrow - this is the only difference with 1.1.0 release for lsc-core, so far. ---------------------------------------- Feature #97: Explicit error message when Rhino fails http://tools.lsc-project.org/issues/show/97 Author: Rapha?l Ouazana Status: Feedback Priority: Normal Assigned to: Rapha?l Ouazana Category: Core Target version: 1.1.1 Hi, When a Javascript script fails, the only error message we get is "Java Null Pointer Exception" or something like that. Rhino can provide much more information simply by displaying the content of the ECMAError that is thrown. I see two solutions for that: - modify BeanComparator to catch the exception thrown by JScriptEvaluator.evalToStringList and JScriptEvaluator.evalToString - modify JscriptEvaluator to catch the exceptions sent by .exec() and modify JScriptEvaluatorTest accordingly I can provide a patch for one or other solution. Regards, Rapha?l Ouazana. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20090930/db1ea60e/attachment.htm>
