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=13565>. 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=13565 To "errors", add prefix, suffix, header, footer attrs, to "messages", add prefix, suffix attrs ------- Additional Comments From [EMAIL PROTECTED] 2002-10-12 04:23 ------- Funny, I didn't remember seeing your note. I ran into this issue at work, which is why I suggested it. In your note, you also suggest the following features: 1. A "scope" attribute, for looking for the messages in a different scope than "request". This seems useful, but I don't have a good feel for what other impacts this might have. I don't know whether the present api for creating messages makes it convenient to place them into anywhere but request scope. 2. A "remove when read" flag, to make messages go away after they are read. This sounds pretty funky. I think you'd be better off having your Action class use an object or collection to store the things you want to write messages for, and when you read an entry off that list to create an ActionError for, then also remove it from the list. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
