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=23186>.
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=23186

Add ability to html:errors tag to override the default settings for header, footer, 
prefix and suffix in resource file





------- Additional Comments From [EMAIL PROTECTED]  2003-09-15 21:44 -------
The last time I updated this my comment got lost so here it is again.
-------------

Hi David,

Apparently my description of the bug is not clear to you. I have reopened it 
once again with additional comments. Basically it goes like this. Neither the 
errors tag nor the messages tag allows us to control its output at runtime. I 
appreciate your recommendation of the messages tag and it would solve the 
issue in some cases but it can not address the following issue.

Assume you have a collection of 4 errors that you want displayed in a box as a 
bulleted list and this form of error output is not the same as it is on some 
of the other pages. The errors tag is out of the question because it only 
allows for one form of output defined in the resource file. The message tag 
gets us one step closer but not all the way. We don’t have to have a runtime 
header and footer. This can be done by wrapping the whole tag call in some 
html. This is the functionality provided by the messages tag. The thing that 
we need to control in this scenario is the bullets. When the tag iterates over 
the messages and outputs them the messages tag gives us no ability to specify 
how each message should be output. In other words it does not give us access 
to the prefix and suffix of each error. If it did then we could specify as a 
prefix something like &#149;&nbsp; to get a bullet in front of each error 
message.

Currently the only way to accomplish this kind of output is to 
a) Put the formatting in the message text itself. This is not good because if 
you are sharing messages you don’t always want them to be output in this way.
b) Write a lot of code in the jsp to fish out the ActionErrors, and iterate 
over them calling <bean:message key=””/> on each one getting the message text 
and wrapping that in the proper html. This is also not a good solution as it 
should not be necessary when we already have tags like messages and errors 
that only require a little more code to add this feature.
c) Write a custom tag that extends the errors tag that allows you to specify 
these values at runtime which I have done but feel this feature should be a 
part of the standard library.

I hope this better explains my case and clears the confusion around header, 
footer, prefix and suffix.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to