Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
From: "Rob S." <rslifka@home.com>
To: <tomcat-user@jakarta.apache.org>
Subject: RE: Exceptional Question
Date: Thu, 6 Jul 2000 20:14:07 -0700
Message-ID: <001201bfe7c1$6969a9a0$39117118@rct1.bc.wave.home.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3964BEF0.DEC76721@eng.sun.com>
Importance: Normal

> In the Struts framework (http://jakarta.apache.org/struts), I approached
> this
> issue by having a validate() method in my form bean return a String
> array of
> messages for all of the errors that have been detected, rather than
> throwing
> exceptions on individual fields.  That way, I can display all the errors
> at
> once.

Ahhh k, those messages being keys to the MessageResource and set to the
localized message, displayed using <struts:error/>.  I gave a preliminary
read through the MVC intro doc, which was a rock and roll adventure.  I've
only heard of it before, so it was sort of thick.  I'm sure the more
experienced web people will probably get it a lot more quickly tho'.  What I
*do* like is the use of an errors collection & keys, which makes things
like:

<%= errors.get(Bean.ATTR_ERROR) %>

much cleaner than having to deal with individualized exceptions and more
flexible than only being able to display the latest error.  Less powerful &
efficient overall, but perhaps more appropriate for small-time sites (mine
included).

One thing I'm tempted to do is figure out elegant ways to only use
get/setProperty to get all of my bean work done.  Doesn't usually turn out
that way tho' =)  I wonder if the next JSP spec will provide more powerful
bean tags.

- r