Mailing-List: contact struts-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <struts-dev@jakarta.apache.org>
Date: 19 Nov 2002 20:04:25 -0000
Message-ID: <20021119200425.28323.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: struts-dev@jakarta.apache.org
Cc: 
Subject: 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:   <mailto:struts-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@jakarta.apache.org>