Dan Allen wrote:
In short, instead of keeping around the DTO, just keep around a key
to get to that DTO, whether in a hidden field or the session. Then,
you can call up the DTO at any point, update it and push it back to
the persistence layer when you want to save it. The nice part about
this tec
Ted Husted ([EMAIL PROTECTED]) wrote:
> Value Objects, also called Transfer Objects, are a design pattern. The
> idea is that you can minimize the calls to the business tier by
> collecting all the data you might need at once and submitting it as a
> batch. (Opposed to, say, updating a form a
From: Darren Hartford [mailto:[EMAIL PROTECTED]
Sent: 03 October 2003 14:26
To: Struts Users Mailing List
Subject: RE: newbie: Best Practice Struts/Value-Objects?
To make sure I understand, the options so far are to:
1. Pass the full VO to the view, create the 15 other fields as hidden tags
w
Struts Users Mailing List'
Subject: RE: newbie: Best Practice Struts/Value-Objects?
Maybe make what we call a displayBean in our app. It is not a VO as we view
VO's to be more domain oriented. It's just for the front end. In your
action create the display bean and set it on the form.
Could you not, then, consider ActionForms and DynaActionForms xfer objects?
Mark
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2003 2:42 PM
To: Struts Users Mailing List
Subject: Re: newbie: Best Practice Struts/Value-Objects?
Value Objects
, October 02, 2003 2:20 PM
To: Struts Users Mailing List
Subject: RE: newbie: Best Practice Struts/Value-Objects?
Hi John,
Yeah, that is one (messy) solution to my problem. My concern is I would have
to do add those 15 fields in every JSP page that sends the VO back, and if I
have to make a chang
Write a tag that emits the hidden stuff. Put it everywhere. Then there's
only one maintenence point...
Hi John,
Yeah, that is one (messy) solution to my problem. My concern is I would have
to do add those 15 fields in every JSP page that sends the VO back, and if I
have to make a change to the
Value Objects, also called Transfer Objects, are a design pattern. The
idea is that you can minimize the calls to the business tier by
collecting all the data you might need at once and submitting it as a
batch. (Opposed to, say, updating a form a line a time.) The properties
on the Transfer Ob
al Message-
From: Menke, John [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2003 12:16 PM
To: 'Struts Users Mailing List'
Subject: RE: newbie: Best Practice Struts/Value-Objects?
you could use hidden variables on your jsp page to store the VO attributes
you are not changing and
List'
Subject: RE: newbie: Best Practice Struts/Value-Objects?
Hi Darren,
I was under the impression that it works exactly the way you hope it
does.
Actually I'm pretty sure it does.
Also what might be worth looking at ( I have to look at it myself ), is
Light-value-objects where you on
Hi Darren,
I was under the impression that it works exactly the way you hope it
does.
Actually I'm pretty sure it does.
Also what might be worth looking at ( I have to look at it myself ), is
Light-value-objects where you only populate the initial value object
with the 5 fields rather than the who
11 matches
Mail list logo
