FormBean

Then, the name of the class goes well with what people call it.  You 
don't have a disconnect.  If we're changing names, this is the 
convention I would use for this.

(
    .. and then you could do:
        - DynaActionFormBean
        - DynaValidatorFormBean
        - ...

    I know it kind of belabors the point, but it's probably easier 
understood to use such nomenclature.
)

Bartley, Chris P [PCS] wrote:

>I'd add that even "Form" could be confusing to some.  Based on the number of
>posts to this list, there appears to be a large percentage of new users who
>don't understand that both GET and POST requests can populate a form bean
>(and that you don't need a <form>...</form> to do it).
>
>I'm not sure what a good alternative would be for ActionForm, however.
>RequestBean?  RequestParametersBean?  CrapIWantTheActionToUseBean?
>SasquatchBean*? ;-)  I'll leave that decision up to those more creative with
>words than I.  :D
>
>chris
>* <grins-at-James-Mitchell/>
>

-- 
Eddie Bush




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

Reply via email to