--- Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> Do you need it?
Yes.
> Back/Forward navigates between resources. Resource
> is an Action, not a
> JSP nor an ActionForm. So, to use default
> Back/Forward functionality
> you need to define as many action mappings as you
> have "navigatiable"
On 8/10/05, Leo Asanov <[EMAIL PROTECTED]> wrote:
> That's the first thing I thought of. But in that case
> you loose "Back" function (and maybe something else as
> well).
Do you need it?
> You could do something if user presses "back"
> on the page, but you can't do much if he clicks "back"
> in
That's the first thing I thought of. But in that case
you loose "Back" function (and maybe something else as
well). You could do something if user presses "back"
on the page, but you can't do much if he clicks "back"
in the browser unless you write your own request
handler. And I am trying to avoid
Could you just put all of your completed ActionForms in a
session-scoped collection, then loop through that collection when the
user clicks "Finish"? This isn't a standard procedure, to my
knowledge, but it would be the first approach I would take given
similar requirements.
-- Jeff
On 8/10/05,
You may lose *automatic* validation... remember that there is no technical
reason you have to use ActionForms at all, and if you do use them there is
nothing that says you have to associate them with Action Mappings.
For instance, I have seen some situations where developers didn't want the
auto-p
Michael, I don't think I really understand your
suggestion. Don't I loose struts validation
functionality if I don't have an ActionForm per html
form?
Cheers,
Leo
> ActionForm does not have to correlate to HTML form
> one-to-one. You can
> create one ActionForm with session scope and use
> neste
ActionForm does not have to correlate to HTML form one-to-one. You can
create one ActionForm with session scope and use nested DTOs/BOs for
each HTML form. For relatives' form you can use a list of nested DTOs.
It is even simpler that you do not need to render a particular
relative, you just enter
Yes, I am talking about one form per request
situation. I don't really see how I can use it as it
is. ActionForm object will be overriden with the
latest one and all previous data will be lost.
Ideally I would prefer to have all data stored in the
session automatically and only when user clicks
"
Leo Asanov wrote:
Is there any standard ways to manage multiple
instances of one form with Struts? I have application
which is supposed to take theorerically unlimited
number of person's descriptions. Every time user
clicks "add one more person" he/she gets exactly the
same form (with the same va
On 8/8/05, Leo Asanov <[EMAIL PROTECTED]> wrote:
> Michael,
>
> I don't see the analogy with "Save As" dialog. And
> ActionForm is not a businees object indeed. Don't know
> what to do with this valuable information though...
>
> If there is nothing in Struts which can help me then
> it is the in
Michael,
I don't see the analogy with "Save As" dialog. And
ActionForm is not a businees object indeed. Don't know
what to do with this valuable information though...
If there is nothing in Struts which can help me then
it is the information I am looking for.
Although I would appreciate any ide
If you need to save document from Microsoft Word, you open "File Save"
dialog. When you need to save another file, do you create another
"File Save" dialog? Do all these dialogs remain allocated until you
shut down the system?
ActionForm is not a business object.
Michael.
On 8/8/05, Leo Asanov <
Hi!
Is there any standard ways to manage multiple
instances of one form with Struts? I have application
which is supposed to take theorerically unlimited
number of person's descriptions. Every time user
clicks "add one more person" he/she gets exactly the
same form (with the same validation rules)
13 matches
Mail list logo
