Thank you d. :-)
newton.dave wrote:
>
> If the forward isn't a redirect you shouldn't need to
> repopulate the form. This use-case, btw, is what
> "mapping.getInputForward()" is for (along with the
> "input" attribute of the action configuration
&g
Hello,
When the user submits my form,
I retrieve it as a DynaActionForm, do some checks in execute() method,
and if the form submitted is not valid,
I want to forward to the form again and repopulate the form with the
inserted values.
How can I achieve this ?
[...]
if( ! valid ) {
// Instruc
Instead of having one front servlet, have one servlet for one action.
Sounds more oriented object to me.
newton.dave wrote:
>
> --- debussy007 <[EMAIL PROTECTED]> wrote:
>> what is the benfit of having the front controller
>> dispatching the request to the appropria
Hi,
My web application allows a user to authenticate via a database.
When he submits his username and password, the request goes to the
AuthentificationAction.
In this action, I want to clean the session if he already had something in
the session
(e.g. he connected with a username and then he wa
I just found out this wonderful attribute "redirect" in the forward element
!
Thank you all.
debussy007 wrote:
>
> Hello all,
>
> I am quite beginner and need some help with the flow of my application.
>
> When a user click on the Back Button from a specific
Hello all,
I am quite beginner and need some help with the flow of my application.
When a user click on the Back Button from a specific page, the last request
is called again,
How can I avoid this behaviour ?
See below for the concrete situation where this is a problem for me :
I have a first
Hello all,
I understand the benefit of having a controller for each possible user
action.
But what is the benfit of having the front controller dispatching the
request to the appropriate controllers ?
Why not calling the appropriate controller directly ?
Thank you for any help.
--
View this mes
7 matches
Mail list logo