Issue #97 has been updated by Jonathan Clarke. Category set to Core Status changed from New to Assigned Assigned to set to Rapha?l Ouazana
Hi Rapha?l, Rapha?l Ouazana wrote: > 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. Thanks for that. After a quick discussion, we feel the second solution would be best. Indeed, this leaves all JScript code in one class. Looking forward to your patch :) Jon ---------------------------------------- Feature #97: Explicit error message when Rhino fails http://tools.lsc-project.org/issues/show/97 Author: Rapha?l Ouazana Status: Assigned Priority: Normal Assigned to: Rapha?l Ouazana Category: Core Target version: 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/20090710/e1cf039d/attachment.htm>
