For struts - fwd the formbean in multiple JSP-action-JSPs

Question

Hello All,
I know this is EJB forum but just I had one Qn so posting.
I know you all must be doing struts as you are doing EJbs.
I have following things and I want to HIT the DB only at last JSP
submit click. How do I keep the formbeans ?
READ EVERYTHING CAREFULLY ---------
I can use session but, I want request or some similar way, or
if there is any thing struts way,
if all is not possible then I will go for session.
Please don't tell me any request or action chaining because
that is not something the case here and as it is highly discouraged
I am NOT going to use that. its not that case anyways,
JSP 1 - has a formbean 1
- submit - goes to Action1
ACTION1 - get the formBean1 ( I get the values1 here hahahaha)
do any processing on formBean1 if needed
set the formbean1 in request ( i am doing this )
mapping.findfwd("success") - to JSP 2
JSP2 - <%get the formbean1 from request and SOP it
(I get the values1 here hahaha) %>
has its own field and formBean2
submit - goes to Action2
ACTION2 - get the formBean2 (I get the values2 haha)
get the formBean1 (I get NULL ?????)
Point is I want to set the formBean1 from request
orginating from JSP2 -submit. JSP2-formBean2 gets submitted there
properly but how can keep fwding formBean1.
Please don't tell me to keep ALLL formBean1 values as hidden
in JSP2. as its not good logic and its tooo much values. etc. etc.
As a matter of fact I have 4 such JSPs and if user selectes codes
on page 4 then only send all earlier 3 formBeans + current formBean4
to DB, else ignore all ( means just ignore, go to new jsp or main menu
let all formBeans garbage collected... hahahaha )
How can I do this ?
I will reply to any Qn s immly as I am in hurry....delivery is very very near
guys ..........:)
anyways,
Enjoy the coding.....!!!
Sandeep

Answer 1

Off hand, the only thing I can think of is to create two completely separate projects.
However, if you want to maintain a good development team and project, I suggest you keep it as one project and not try to hide anything from one group of developers. Instead, install CVS as your repository. It will track what changes were made and by who and you can roll back to a previous version of a JSP or java class if necessary. Your team should be briefed on the architecture you decide on (Spring, Sturts, etc), and basic good coding practices you want enforced.
Here are a few rules:
* nothing is to be checked into CVS that doesn't compile cleanly.
* nothing is to be checked into CVS that has any error or warning messages form your IDE outstanding.
* nothing is checked into CVS without the comment field of the commit dialog box being filled in.
* You have one build.xml file that eveyone uses to compile all code.
* All JSP pages are to be well formed xml (no dangling tags).
* all java classes and JSP pages are to be properly indented.
* all classes are to have javadoc describing what a class is for, and all functions are to have javadoc describing what the function does (not how it does it).