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=23005>. 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=23005 html:messages tag does not gracefully handle missing message resource keys. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2003-09-15 02:15 ------- Following refactoring the logging issue is resolved but the setting null in the pageContext issue still remains: TagUtils.message call may still return null if the message resource does not exist. This then try to set null on the pageContext which would fail. The id should be removed as in the doStartTag() method: if (msg != null) { pageContext.setAttribute(id, msg); } else { pageContext.removeAttribute(id); } This way if a message is missing the resulting page will still render rather than experiencing a runtime error. Cheers James --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
