> Jim Seach wrote: > [...] > > Since it's exposing the form values, why not use: > > > > public ActionForm getValue() > > > > This might be more descriptive. we are exposing it in the view, and > > designers might not have a clue what a JavaBean is. That would give > > us: > > > > <input type="text" name="username" value="$form.value.username"> > > Well, I am not fully sold on it.
me neither. it feels like a very misleading name to me. > How about: > > public ActionForm getValues() // note the 's' to emphasize that > // we retrieve multiple values definitely better than getValue(). i could live with this i guess, but i still don't feel it is quite as accurately descriptive as getBean(). we are after all returning a single object that is not a collection (List, Map, array, etc). I don't want designers to get the idea that they could do a #foreach on it. i do see that $form.values.username could be more comfortable to a designer unfamiliar with the concept of javabeans, but i don't think it's a big issue. besides, even struts/jsp uses the term 'bean' in its tags. i doubt any designers will struggle with it. > public ActionForm getFormBean() blech. redundancy. -1 > Or, we rename the $form tool to $formtool and name the method getForm() > This would make: $formtool.form to access the form. blech again. -1 > Or, we just keep the getBean() Method. It should be easy for designers > to get the concept. +1 (but i can live with getValues() if i'm outnumbered on this one.) Nathan Bubna [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
