Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve error reporting in StandardScriptEvaluator [SPR-13557] #18133

Closed
spring-projects-issues opened this issue Oct 9, 2015 · 1 comment
Closed
Assignees
Labels
type: enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Oct 9, 2015

Juergen Hoeller opened SPR-13557 and commented

Along the lines of #18066, there's an opportunity for providing analogous improvements in StandardScriptEvaluator, replacing the rather convoluted ScriptException stacktrace output with a more focused evaluation error message.

On a related note, GroovyScriptEvaluator doesn't consistently catch and wrap exceptions coming out of Groovy eval calls, which should get revised along with StandardScriptEvaluator for reasonably equivalent output.


Affects: 4.2.1

Issue Links:

  • #18066 Improve error reporting for template rendering in ScriptTemplateView
  • #18069 Revise script engine retrieval for better error reporting
@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Oct 9, 2015

Juergen Hoeller commented

StandardScriptEvaluator uses the same eval exception exposure as ScriptTemplateView now, through a shared StandardScriptEvalException in the scripting.support package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants