I tried to break my long-form like below.
<html:form action="whatever">
<jsp:include page="part1.jsp" flush="true"/>
<jsp:include page="part2.jsp" flush="true"/>
</html:form>
But could not succeed. I checked the struts 1.0 version and there's no
different in related code as its still putting the bean in Page scope. Can
somebody confirm if this is solved in struts 1.1 ?(though I got it to work
by chaning appropriate line in FormTag.java).
Thanks,
Tahir
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Saturday, October 06, 2001 4:35 PM
To: [EMAIL PROTECTED]
Subject: Re: struts-tags - long form problem
----- Original Message -----
From: "Tahir Awan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, October 06, 2001 3:56 AM
Subject: RE: struts-tags - long form problem
> Thanks a lot for this valuable info. Actually I have a version retrieved
in
> last December and modified some tags and wrote some new tags to fit our
> needs (I am only using taglibs from the struts framework).
> But it looks like to solve this problem, I have to acquire the latest
> version and redo my changes.
If you think the changes you made to the Struts tags might be useful
extensions, then you could propose them as such on the struts-dev mailing
list.
> I have all the forms with a Custom Type (PageBean) which is wrapper around
a
> Collection and like this idea because I dont have to create a new javabean
> for each view.
>
> So the question is whether the included jsp files (fragments) will still
> read properties from form's bean?
Yes, they will.
--
Martin Cooper
>
> Tahir
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Sent: 10/5/01 11:34 PM
> Subject: Re: struts-tags - long form problem
>
> Actually, it is possible, and it is the only solution I am aware of. I
> know,
> because I rely on this heavily to solve exactly the problem you are
> having.
> :-}
>
> Early versions of Struts stored form-related data in page scope, which
> prevented the use of nesting in the way you describe. However, some time
> ago - before the Struts 1.0 release - this was changed so that the
> form-related data is stored in request scope.
>
> This makes it possible to break up your pages like this:
>
> <html:form action="whatever">
> <jsp:include page="part1.jsp" flush="true"/>
> <jsp:include page="part2.jsp" flush="true"/>
> </html:form>
>
> Incidentally, questions on Struts-related tags are better asked on the
> struts-user mailing list.
>
> --
> Martin Cooper
>
>
> ----- Original Message -----
> From: "Tahir Awan" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, October 05, 2001 2:46 PM
> Subject: RE: struts-tags - long form problem
>
>
> > That's not possible because all of the tags have to be nested inside
> > struts:form tag (otherwise they wont render).
> >
> > Tahir
> >
> > -----Original Message-----
> > From: Lavandowska
> > To: [EMAIL PROTECTED]
> > Sent: 10/5/01 5:01 PM
> > Subject: Re: struts-tags - long form problem
> >
> > --- Tahir Awan <[EMAIL PROTECTED]> wrote:
> > > I can't break the page because all the tags have to be nested in the
> > > <form>
> > > tag. Is there any workaround?
> >
> > I'm not saying this is a "good" solution, but you could break it up by
> > putting parts into other .jspf (fragment) files and using <jsp:include
> > /> to execute them.
> >
> > Lance
> >
> > __________________________________________________
> > Do You Yahoo!?
> > NEW from Yahoo! GeoCities - quick and easy web site hosting, just
> > $8.95/month.
> > http://geocities.yahoo.com/ps/info1
>
