I have 3 actionform classes AForm, BForm, and ABForm. AForm and BForm
contain only normal String fields (with getters/setters), while ABForm
contains instances of AForm and BForm (getters only).
I want to use nesting in my JSPs to promote consistency/eliminate redundant
work, so for example, ab.jsp looks like this:
<!-- ab.jsp -->
<nested:root >
...
<nested:nest property="a" >
<jsp:include page="a.jsp" flush="true"/>
</nested:nest>
...
<nested:nest property="b" >
<jsp:include page="b.jsp" flush="true"/>
</nested:nest>
...
</nested:root>
a.jsp and b.jsp are wrapped with nested:root (as the above ab.jsp is) to
make the jsp:includes work.
My webapp can use either AForm alone, BForm alone, or ABForm. On starting
my webapp, whichever form the user calls first works, but then the other
forms fail when called. The nested tags seem to save something (must be in
either session or application scope?) that confuses property names and cause
subsequent calls to the other forms to look for properties from the first
form called.
Can anyone suggest what I've got wrong? My understanding of nested tags is
not 100% clear.
Brian
PS My webapp is configured so that /form/ab.do, /form/a.do or /form/a.do,
will call either abform.jsp, aform.jsp or bform.jsp:
<!- abform.jsp -->
<nested:form method="get" action="/form/ab.do" >
<jsp:include page="ab.jsp" flush="true"/>
<p><nested:submit /><html:reset/></p>
</nested:form>
<!- aform.jsp -->
<nested:form method="get" action="/form/a.do" >
<jsp:include page="a.jsp" flush="true"/>
<p><nested:submit /><html:reset/></p>
</nested:form>
<!- bform.jsp -->
<nested:form method="get" action="/form/b.do" >
<jsp:include page="b.jsp" flush="true"/>
<p><nested:submit /><html:reset/></p>
</nested:form>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
