w Tomaka
Subject: Re: Two Forms, Two Form Beans, One JSP
You can have multiple forms on the same page. I am using Tiles. I put
some forms in the header/footer and they work just fine. I had to use
different actions for the two forms, and I had to use session scope for
one of them in order to
On 7/7/05, Abdullah Jibaly <[EMAIL PROTECTED]> wrote:
> No, I actually meant that Struts will only process and associate one form
> with the action processing that request, and therefore any validation, etc.
> So only one html form will get associated with the current ActionForm, even
> with ses
page.
Regards,
Abdullah
-Original Message-
From: Michael Taylor [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 07, 2005 1:02 PM
To: Struts Users Mailing List
Cc: Andrew Tomaka
Subject: Re: Two Forms, Two Form Beans, One JSP
You can have multiple forms on the same page. I am using Tiles
I read this post several times. If I understood it, the key is this line:
"...the action responsible for this needs the name attribute set to the
Form Bean of the first form..."
If I read this to mean you want a post to form A to update form B so that it
has access to the state of submission t
user@struts.apache.org
Subject: Two Forms, Two Form Beans, One JSP
Hey all,
I'm attempting to create a JSP that is made up of two forms. Each
form needs a different form bean and is processed by a different
action. The catch is that the first form returns back to the JSP and
the action responsibl
This is what I've ended up doing for now. I have my one form bean for
both forms since the data is related.
What if the data isn't related though? Does Struts provide a simple
solution or is just an area to hack around? I can accept the latter
since it's expected when using a framework.
Either
You could use frames for the bottom portion. Then you really *could*
treat them as two separate pages because, well, they are!
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
On Thu, July 7, 2005 1:32 pm, Andrew Tomaka said:
> Using a nested
Using a nested form bean may actually be a viable solution that I'll
have to look in to. Ideally though, I'd be able to treat the two
different forms as two separate pages that just happen to share the
same screen space. I guess that's the downside to using a framework:
you can't always get what y
Andrew Tomaka wrote the following on 7/7/2005 12:00 PM:
I imagine I've over complicated the problem,
Yes, I think you are:)
My problem is that I have a "PreAction" to do the processing on the
form. This requires the page to have the form bean assigned to it.
Since I have two different forms
Andrew,
if the data being edited in the two forms are related, then for the
child data you could use a nested bean as an attribute on the form.
The parent data would remain as usual directly in the form.
Adam
Andrew Tomaka on 07/07/05 17:46, wrote:
I did consider using a single form bean fo
Does the ActionForm for the bottom form only come into play when a
selection is made in the upper form?
If so, you could always instantiate the ActionForm yourself, populate it
as appropriate in the Action that fires when that selection is made, shove
it in request and deal with it manually.
One
I did consider using a single form bean for both forms, but it didn't
really sit well with me from a design stand point. We have two
different forms doing two different things so there should be two
different beans. Heck, if I had it my way, the two forms would be on
separate pages (wizard style)
From: "Andrew Tomaka" <[EMAIL PROTECTED]>
> My problem is that I have a "PreAction" to do the processing on the
> form. This requires the page to have the form bean assigned to it.
> Since I have two different forms doing two different things, I should
> have two different form beans, but I don't
hanks,
-Original Message-
From: Andrew Tomaka [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 07, 2005 12:00 PM
To: Struts Users Mailing List
Subject: Re: Two Forms, Two Form Beans, One JSP
I imagine I've over complicated the problem, so I've taken a step back
and am looking at it fro
I imagine I've over complicated the problem, so I've taken a step back
and am looking at it from the beginning again. The following are my
basic requirements:
When the user makes the first request, they are taken to a page with a
drop down menu. This drop down menu is built from information stor
On 7/7/05, Andrew Tomaka <[EMAIL PROTECTED]> wrote:
> Hey all,
>
> I'm attempting to create a JSP that is made up of two forms. Each
> form needs a different form bean and is processed by a different
> action. The catch is that the first form returns back to the JSP and
> the action responsible
Andrew Tomaka wrote the following on 7/7/2005 10:26 AM:
I'm attempting to create a JSP that is made up of two forms. Each
form needs a different form bean and is processed by a different
action. The catch is that the first form returns back to the JSP and
the action responsible for this needs
ssage-
From: Andrew Tomaka [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 07, 2005 9:26 AM
To: user@struts.apache.org
Subject: Two Forms, Two Form Beans, One JSP
Hey all,
I'm attempting to create a JSP that is made up of two forms. Each
form needs a different form bean and is processed by a
Hey all,
I'm attempting to create a JSP that is made up of two forms. Each
form needs a different form bean and is processed by a different
action. The catch is that the first form returns back to the JSP and
the action responsible for this needs the name attribute set to the
Form Bean of the fi
19 matches
Mail list logo
