Joseph wrote:
Now I want to do the same thing but use DynaActionForm for my
clientInfoForm,
what should I do to pre-populate it? (there will be no setters any more)
Look at the API docs for DynaActionForm, there are several set methods.
Or use BeanUtils.copyProperties to copy the values over
I'm going to answer my own question:
create the bean for the target builder page in the session scope, not the request
scope. Having several cups of coffee, a walk, and a long think, led me to this logical
conclusion (if I want to manipulate a bean that exists in a session data structure,
I assume that your select tag is expecting to get data from your form object that you
had
previously placed into the request?
When you return to the 'toJsp' page, you will need to place the form object back into
the
request, or place the form object in the session in the first place.
When you
I do the following:
1. Let us say, you want to submit from 'fromPage' and want to do some
pre-processing before you give out 'toPage'.
2. In all my Action objects, I have two methods - 'preprocess()' and
'postprocess()'.
3. I submit ALL the requests from 'fromPage' to the Action object
Many times pre-processing and post-processing are related, and it can be
convenient to handle both in the same Action class.
A good way to implement this is to have a seperate Action Mapping for
each task (pre-process and post-process). Both mappings would point to
the same Action but use
5 matches
Mail list logo
