If you have the HTML in the resources file, you are stuck with that font across the whole application I would think. For a form or something its not bad because you are only going to use that error in one place. But with general errors or messages, you may want the information to be displayed differently depending what page its being displayed on.
of course after reading and trying to implement best practices for the past two months in struts, I am starting to wonder if a "Just do it / damn the torpedos" approach is not a bad idea! Do it the quickest, fastest way. -----Original Message----- From: kkamholz [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 2:10 PM To: struts-user Subject: RE: html:errors Yeah, that's what I do. I make the font part of the header/footer, as well as tags for a list. Then the individual error messages are list items. It creates a very nice display. Some consider it bad practice to use html in your properties file, but others such as myself don't have a problem with it. ~ Keith http://www.buffalo.edu/~kkamholz -----Original Message----- From: Struts Newsgroup [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 12:40 PM To: [EMAIL PROTECTED] Subject: Re: html:errors Subject: Re: html:errors From: Eric Rizzo <[EMAIL PROTECTED]> === [EMAIL PROTECTED] wrote: > Like so? > > <logic:messagesPresent> > <font color="Red"><html:errors/></font> > </logic:messagesPresent> For that why not just put the <font...> and </font> elements as the value of errors.header and errors.footer in your ApplicationResources file? Eric -- Eric Rizzo Software Developer Jibe, Inc. http://www.jibeinc.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
