I would suggest it be done, yes.  You can make certain assumptions about 
a bean - having *Bean as a name immediately tells you certain things 
about a class.  Though, for the dynamic classes, I suppose it's less 
appropriate ...

I'm cool with status quo :-)  But, if change is about us - that's the 
way I personally would like to see it go.

David Graham wrote:

> To be devil's advocate...Why should you append the word "Bean" to your 
> class name?  Should every class that's used as a bean have this word 
> appended to it?  PersonBean, AccountBean, etc...
>
> I see nothing wrong with the current name of ActionForm but Form or 
> FormBean seem appropriate as well.  In this case, adding Bean to the 
> end is appropriate because it's not meant to be used outside of a web 
> framework.
>
> Dave 

Peace :-)

-- 
Eddie Bush




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

Reply via email to