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=7097>. 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=7097 when bean has null value for PresentTag exception is saved, even though value is cleared ------- Additional Comments From [EMAIL PROTECTED] 2002-03-13 21:24 ------- ooops...hit the committ button by accident... Like I was saying, value is set to 'null', but shouldn't the savedException be cleared as well? It's not really an exception that should be saved because the tag did not behave according contract. It's the utility method (i.e RequestUtil.lookup()) that does not behave according to contract...but this exception is trapped...so it should not be saved. I don't have a patch for this at this time, but I'll try to get one in when I get a chance. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
