struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iain Sanderson" <>
Subject RE: HOWTO pre-populate forms with data, then update ?
Date Thu, 23 Jan 2003 20:53:52 GMT

I'm really doing precisely this - but I don't know how to transfer the 
data from the business logic to the form bean underlying the the page 
view. My kludge is to get around this deficiency.  How is it done?


Please respond to "Struts Users Mailing List" 
To:     "Struts Users Mailing List" <>

Subject:        RE: HOWTO pre-populate forms with data, then update ?

In general, Struts applications will use "prepare actions" to prepare
the data for a form, and "process actions" to process the submitted data
for a form.  In your "prepare action" code, you'll interface with your
business logic to obtain the required data, then populate fields of a
bean, probably in request scope, not session scope, then you'll forward
to your page view, which will use the request scope bean to populate the
form.  Your "process action" will then take the fields from the form
(populated from the HTML fields) and send the changed values to your
business logic.

Usually, you can avoid putting most of this bean data into the session

-----Original Message-----
From: Iain Sanderson [] 
Sent: Thursday, January 23, 2003 12:21 PM
Subject: HOWTO pre-populate forms with data, then update ?

Newbie question:

I've managed to use Struts forms as a means of  initial data entry ( 
registration forms etc) but have got  stuck on how to use a form to
data that already exists in a database. For example, a form where a user

can update their user details (address, email etc) and then submit the 
updates. How is this best done in struts ?

I'm sure there's a good way of doing this, but my Kludge so far has been

to  create a bean in the session scope containing the data I want to 
populate the form with ( eg a user's current address), and then use
 html:text  tags to view  the bean data using their "name" and
attributes.   Once the user has submitted their updates, the ActionForm 
accesses the form bean to obtain the updates, and applies the updates to

the database.   I then of course have to update the  original bean's
with the new values ( eg their amended address) and send it back into
session scope.  It's a bit of a mess, but it works. 

I know there's a better way. Please help. Thanks.

Iain Sanderson

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message