PROPOSE: extension of tag

[Oleg V Alexeev <go...@penza.net>]

Hello friends,

 I propose to make errors rendering in <form:errors/> tag more
 flexible. Now header and footer for errors list can be specified
 only. All other html tags must be incorporated to resources. Each
 error string has identical html parts, located around textual error
 message. This parts (start single message, end single message, etc. )
 can be defined in resources, separately from error messages.
 
 Ability to list sources of errors (properties) and print errors for
 some property separately can be used as ability to print whole list
 of error messages, structured by source names.

 Each property name can used as key to search for string in resource
 bundle and place this string as label for chapter in errors list.

 For example, set of strings to form errors list can be defined by
 this way:

 whole errors list header -
  org.apache.struts.errors.header
 whole errors list footer -
  org.apache.struts.errors.footer
 header for report for single property
  org.apache.struts.errors.prop.header
 footer for report for single property
  org.apache.struts.errors.prop.footer
 header for property name
  org.apache.struts.errors.prop.name.header
 footer for property name
  org.apache.struts.errors.prop.name.footer
 header for list of errors for single property
  org.apache.struts.errors.prop.messages.header
 footer for list of errors for single property
  org.apache.struts.errors.prop.messages.footer
 header for single message
  org.apache.struts.errors.prop.message.header
 footer for single message
  org.apache.struts.errors.prop.message.footer

 I already use this scheme and can send to community code with support
 of listed features.

-- 
Best regards,
 Oleg                          mailto:gonza@penza.net