I'd agree with Edgar. Since ActionForms are a class rather than an
interface, as it stands, you either have to live with the duplicate
objects, or least two sets of properties, or go to other extremes. You
can do things like use the ActionForms as an adaptor or facade for your
business objects,
Ok, but I'm not suggesting the request be saved or serialised.
-Original Message-
From: Edgar P Dollin [mailto:[EMAIL PROTECTED]
Sent: 17 September 2003 15:16
To: Struts Developers List
Subject: RE: Conceptual question about populating/validating values
I test my apps under tomca
Developers List
> Subject: RE: Conceptual question about populating/validating values
>
>
> I'm assuming the same thread handles the client request all
> the way through - which is the case in my environment (which
> environments should I steer clear of?). If this is the case
riginal Message-
From: Edgar P Dollin [mailto:[EMAIL PROTECTED]
Sent: 17 September 2003 13:08
To: Struts Developers List
Subject: RE: Conceptual question about populating/validating values
If you are saving system objects, i.e. request, to persistent objects,
you
will have synchronization prob
o: Struts Developers List
> Subject: RE: Conceptual question about populating/validating values
>
>
> I hit the same problem. I don't like having two fields
> (string and type
> specific) as you have to sync. them and it bloats your
> objects out. I don't like the
x27;Struts Developers List'" <[EMAIL PROTECTED]>
Betreff: RE: Conceptual question about populating/validating values
> If I were you I would use strings in my form beans (or at least methods
or
> parallel field which accept strings as arguments) and look into third
nverter, so you can build any validation errors there.
Regards,
Graham.
-Original Message-
From: Edgar P Dollin [mailto:[EMAIL PROTECTED]
Sent: 17 September 2003 12:33
To: Struts Developers List
Subject: RE: Conceptual question about populating/validating values
If I were you I would use
er 17, 2003 6:23 AM
> To: [EMAIL PROTECTED]
> Subject: Conceptual question about populating/validating values
>
>
> Hi there,
>
> I have a conceptual question about the population process for
> properties inside Struts.
>
> First of all a description:
>
&
Hi there,
I have a conceptual question about the population process for properties
inside Struts.
First of all a description:
I have a JSP which includes a text input field like this:
"currentPerson" is a Person-Object which has a birthDate-Attribute of type
java.util.Date (!).
This object is
