Ok, thanks Hubert - this confirms that I will have to do what I want another way.
Cheers
Conrad
Conrad CramptonSoftware Solutions ManagerForce Headquarters11 Edinburgh SquareSutton RoadMaidstoneME15 9BZ01622 653283 (ext)19-3283 (internal)07814 011752 (mobile)>>> [EMAIL PROTECTED] 20/01/05 15:36
Our views align on the use of session scoped beans, however, it seems
that session scope is what meets your needs.
> So this essentially means that nested objects are worthless as you can't
> keep reference to child objects that you populate in the middle tier for the
> trip around to the UI and
Conrad CramptonSoftware Solutions ManagerForce Headquarters11 Edinburgh SquareSutton RoadMaidstoneME15 9BZ01622 653283 (ext)19-3283 (internal)07814 011752 (mobile)>>> [EMAIL PROTECTED] 19/01/05 16:07:49 >>>
> So the question is this - how do I retain values of nested properties that> aren't r
> So the question is this - how do I retain values of nested properties that
> aren't required to be (or cannot be) represented in the jsp?
The only values that you'll get when the form is submitted are the
values that the form has.
If you have values that you want to submit with the form, but do
The ActionForm you specified in your ActionMapping in
struts-config.xml under the name attribute, e.g. "logonForm", is
available to you in the execute method. Just cast your ActionForm
parameter to the particular form you used with the Action, e.g., if
you have
public ActionForward execute(Action
From: "Roland Carlsson" <[EMAIL PROTECTED]>
> When you say that the newinsurance.jsp "just see it" where do you store
> "it"? In request.setAttribute() with some key? Session?
You don't have to store it anywhere... it's already there. In the 'execute'
method signature, you are given a _reference_
Every JSP page in my application is going to have two actions associated
with it. One action will always be called prior to displaying the JSP
page. The other will be called to process the user's input. In the
struts-config, both of these actions are configured with the same form
bean. Thus
Roland,
I dont know if this solution is not the approved way but I do the following.
I have a CreateForm which extends the ActionForm. It contains all the
properties that map to the database and the validation rules.
I then have an UpdateForm which extends the CreateForm and implements its
paren
8 matches
Mail list logo