Paul Sundling wrote:
After rereading it again I think I should clarify one of my comments:
"Even generating nothing would seem to be prefereable!"
What I meant by that is the tag itself generating nothing (resulting
in an empty select list) as opposed to the entire page generating
nothing(current behavior).
That would be very much appreciated.
You can file a Bugzilla report with your patches attachment.
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.)
Paul Sundling
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Robert Leland [EMAIL PROTECTED]
------------------------------------------
Java, J2EE, Struts, Web Application Development
804 N. Kenmore Street +01-703-525-3580
Arlington VA 22201
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
