Probably because you want to remain faithful to the MVC approach: only the
controller should decide where to dispatch a request. Linking JSPs together
directly can lead to a spaghetti mess. What you want is one central point
where the request dispacthing is done (the ActionServlet) so you can easi
Oops forget my answer, I did not read well enough the question in the first
instance, sorry.
Fr.
-Original Message-
From: Rey Francois
Sent: 02 July 2001 18:56
To: '[EMAIL PROTECTED]'
Subject: RE: jsp vs do
Probably because you want to remain faithful to the MVC approach
e actions do not need any input at all. (e. g.
/admin/restart.do)
It wouldn't be very bad to go directly to login.do without any data, since
this would simply report an error and forward to its input (login.jsp)
itself.
--
gR
>
> -Original Message-
> From: Gregor
/admin/restart.do)
It wouldn't be very bad to go directly to login.do without any data, since
this would simply report an error and forward to its input (login.jsp)
itself.
--
gR
>
> -Original Message-
> From: Gregor Rayman [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July
/logon.do?username=foo&password=bar
Anthony
-Original Message-
From: Gregor Rayman [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 02, 2001 10:28 AM
To: [EMAIL PROTECTED]
Subject: Re: jsp vs do
"Anthony Martin" <[EMAIL PROTECTED]> wrote:
> This is how I understand it.
"Anthony Martin" <[EMAIL PROTECTED]> wrote:
> This is how I understand it. A .do maps to an action then to a .jsp. If
> you link directly to a .jsp, the action never executes. Actions are mapped
> to a .jsp in the struts-config.xml file.
>
> I'm sure there are more clear explanations to foll
This is how I understand it. A .do maps to an action then to a .jsp. If
you link directly to a .jsp, the action never executes. Actions are mapped
to a .jsp in the struts-config.xml file.
I'm sure there are more clear explanations to follow.
Anthony
-Original Message-
From: Bob Byro
7 matches
Mail list logo
