--- Paul Sundling <[EMAIL PROTECTED]> wrote: > I was wondering what the general design philosophy for errors inside > custom tags is. I've noticed that when there's a problem with > <html:option*>, instead of giving a useful error message, it would just > fail to display anything (clean white page). Is that the desired > result? > > I'd be willing to modify the class to use error messages instead of > crashing the page, if I'm not the only one who finds that desirable. > Even generating nothing would seem to be prefereable! (Pointing me to a > > tag with the kind of preferred error handling that I should emulate > would be useful.)
Tags should never print error messages to the screen for the user to see. They should use commons-logging to log a helpful error message. David > > Paul Sundling > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
