I believe your workaround is the recommended approach. That is, use one
form bean for both forms. The form bean could implement two different Form
interfaces (one per html:form) to make the seperation more obvious.
-Original Message-
From: Tim Sawyer [mailto:[EMAIL PROTECTED]]
Sent:
Thats what I figured. Unfortunately I have some generic code for one of the forms (it
does a paged view of the data, 30 rows, 5 rows per page) so the form on this page will
have to be a subclass of the generic one.
Thanks,
Tim.
Jerome Jacobsen [EMAIL PROTECTED] wrote :
I believe your
To be honest, I can't remember. It was a while ago now, and I used the workaround.
Now I'm on a more complex page and it would be neater to have two forms, so I was
thinking before leaping in.
The error was something like a Struts tag looking for a bean and not being able to
find it.
Which
I guess if the app couldn't find the form bean I would look at my struts-config.xml
first to be sure that I had set up the action right. You might need to put the bean
scope at the session level (not always desirable, I know).
Tim Sawyer [EMAIL PROTECTED] wrote:
To be honest, I can't
I actually cut out the forms individually, and tested the page with just one form on
(each form in turn). They both worked fine alone, just not at the same time!
I've worked around again this time.
Tim.
[EMAIL PROTECTED] wrote :
I guess if the app couldn't find the form bean I would look
5 matches
Mail list logo
