picture, and so a field with the same name on two screens
> is in a way incorrect.
>
> Again though, I don't disagree with you or Michael, it's just a
> different perspective :)
>
> > --Brad
>
> Frank
>
>
>
>
>
> >
> > -Original Message-
o: Struts Users Mailing List
Subject: Re: Wizard page "data corruption"
No, I think you misunderstood :)
Let's say we are designing a wizard flow with three pages, plus one
"confirmation" page at the end. Each page has a single HTML form on it.
The first page has this in
-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Wed 11/16/2005 12:23 PM
To: Struts Users Mailing List
Subject: Re: Wizard page "data corruption"
No, I think you misunderstood :)
Let's say we are designing a wizard flow with three pages, plus one
"confirmation" pa
Michael Jouravlev wrote:
Then you display page 2, it loads firstName from
ActionForm and displays it. If you change the name and submit page 2,
it stores changed name back in ActionForm. If you go back to page 1
and the page is not cached, it will be reloaded from server with
updated firstName. S
Oh, stupid me, you are talking about HTML FORM fields, while I was
thinking about ActionForm fields.
Returning to your case, the value does not seem "corrupted" to me. I
think it is normal that different web pages of one wizard would share
data. You display page 1, enter firstName, submit, it is s
No, I think you misunderstood :)
Let's say we are designing a wizard flow with three pages, plus one
"confirmation" page at the end. Each page has a single HTML form on it.
The first page has this in the form:
The second page has this:
And the third page has:
(We're going to ignore
I hope I understand what you are asking. A couple of things come to mind about
threads and Servlets. If one uses Instance variables in Servlets then each
instance of that Servlet has a unique variable and there is no data corruption.
However if one uses Class variables then each instance of
7 matches
Mail list logo