`No, I only have one class:
This is how a bean looks:
public class Content extends ActionForm implements Serializable {
}
So Content can be a data model bean because it has gets/sets but it also can
be a form.
I just made a realization that this isn't cool if I'm working in a larger
environment since any non-struts application/process using this object would
have to have access to ActionForm =\
>From: "David Cypers" <[EMAIL PROTECTED]>
>Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
>To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
>Subject: RE: FormBeans, Data Beans and Databases (oh my)
>Date: Mon, 29 Apr 2002 17:40:50 +0200
>
>The first is I've been taking my data models and making beans out of them
>as
>I should ya? So a user in my "portal" let's call has a UserBean with get()
>set() methods for each of the properties. But for for registering a user,
>struts requires a FormBean. So I've repurposed the same data model bean
>and
>made it a form bean. Is this good or bad?
>
>Do you have 2 identical classes , which are solely different by that they
>are implementing another interface or extending an abstract class? Can't
>you
>make a wrapper class from your FormBean which wraps the UserBean? You can
>do
>this by means of 'delegation'. I think that it's better to use delegation
>instead of keeping 2 copies of the data model( one in the userbean and one
>in the formbean).
>
>D.
>
>
>--
>To unsubscribe, e-mail:
><mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail:
><mailto:[EMAIL PROTECTED]>
>
_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
