On Wed, 2004-08-25 at 15:03, Rick Reumann wrote:
> Sebastian Ho wrote:
>
> > I am already using DispatchAction.
> >
> > I didn't use the scope in my action-mapping. Instead I use
> > session.setAttribute in my Action.
>
> More than likely you don't need to do the above (you can give your form
>
Sebastian Ho wrote:
I am already using DispatchAction.
I didn't use the scope in my action-mapping. Instead I use
session.setAttribute in my Action.
More than likely you don't need to do the above (you can give your form
Session scope right on the mapping for the Action in your config).
The codes
I am already using DispatchAction.
I didn't use the scope in my action-mapping. Instead I use
session.setAttribute in my Action.
The codes to update the actionform is in action1. But I need to update
the same form in action2. One way is to duplicate the same codes in both
action. Or the common up
lixin chu wrote:
so JSP1 should be associated with another Action,
which fetch data from DB and setAttribute in request
or session.
Well everything should be going through an Action of some sort so "yes"
just make sure the form is populated in your Action before forwarding on
to the JSP.
--
Rick
so JSP1 should be associated with another Action,
which fetch data from DB and setAttribute in request
or session.
You should make your Action not the JSP1 available to
the user.
--- Sebastian Ho <[EMAIL PROTECTED]> wrote:
> Hi
>
> Scenario :
>
> 1. User submits form in JSP1 which Action1 save
Sebastian Ho wrote:
Hi
Scenario :
1. User submits form in JSP1 which Action1 saves to database.
2. Action1 set Form1 into session.
3. Action1 forwards to JSP1 again, which is suppose to display newly
added form with other forms previously added.
How do I make JSP1 to get values from database BEFORE
6 matches
Mail list logo