You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2002/11/19 21:04:25 UTC
DO NOT REPLY [Bug 14693] New: -
ErrorsTag.java - Output message key if lookup to message db fails
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14693>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14693
ErrorsTag.java - Output message key if lookup to message db fails
Summary: ErrorsTag.java - Output message key if lookup to message
db fails
Product: Struts
Version: 1.1 Beta 2
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Custom Tags
AssignedTo: struts-dev@jakarta.apache.org
ReportedBy: edgar@blue-moose.net
If an error has been added to a scope but the message key is not in the message
db it is too much work to find the error. It is simpler debugging or even for
the operator if in the case where the message is not found to output the key in
some fashion.
Here is a fix:
249,252d248
< } else if (report.getKey() != null) {
< results.append("Key: ");
< results.append(report.getKey());
< results.append(" not in message DB\r\n");
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>