I stumbled across a nasty glitch by coding this seemingly harmless error
handling in my action:
this.addActionError(exception.getMessage());
which in the ActionErrorTag's freemarker template causes this:
Expression error is undefined on line 4, column 50 in
template/simple/actionerror.ftl.
The problematic instruction:
----------
==> ${error} [on line 4, column 48 in template/simple/actionerror.ftl]
The problem arises when it's a NullPointerException. There's a related Jira
issue (marked as fixed) for Field Errors:
https://issues.apache.org/struts/browse/WW-1208
Shall I reopen this or is it considered a developer error?
regards
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
