-Original Message-
From: Patrick Cheng [mailto:[EMAIL PROTECTED]
Sent: Monday, January 12, 2004 7:34 PM
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: RE: Mandatory use of form rather than request object
Hi,
I understand that the request.getParameter should not be used when
PROTECTED]
Sent: Monday, January 12, 2004 11:25 AM
To: Struts Users Mailing List
Subject: Re: Mandatory use of form rather than request object
This precludes you from storing data in the request scope, though - so
you're left with only storing things in the session scope, which I
wouldn't consider ideal
Message-
From: Andrew Hill [mailto:[EMAIL PROTECTED]
Sent: Monday, January 12, 2004 7:41 PM
To: Struts
Subject: RE: Mandatory use of form rather than request object
Yeh, your right though. Taking it out is a bit drastic and the request
object tends to be needed for various other things as well so
-mind.com/consulting.htm#StrutsMentoring
-Original Message-
From: Patrick Cheng [mailto:[EMAIL PROTECTED]
Sent: Monday, January 12, 2004 7:34 PM
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: RE: Mandatory use of form rather than request object
Hi,
I understand
AM
To: Struts Users Mailing List
Subject: RE: Mandatory use of form rather than request object
Hi ,
Can you elaborate a bit? The situation in my mind is, a jsp page with a
list of records, but no form at all.
Like
a href=details.jsp?id=1Apple/a
a href=details.jsp?id=2Orange/a
Of course
Hi,
Its a good idea to use just form.getAttribute than use request.getparameter..I think
that is major advantage with struts...You should no longer be using this syntax.The
form should be a complete container as far as actions are concerned.The advantage is
that just by looking at the form you
and model.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, January 12, 2004 11:53 AM
To: [EMAIL PROTECTED]
Subject: RE: Mandatory use of form rather than request object
Hi,
Its a good idea to use just form.getAttribute than use
request.getparameter..I
Create a superclass that overides the execute method and calls an abstract
execute method that does not pass the request object.
The subclasses overide the execute method without the request object being
passed.
Also look into the ProcessAction, which is part of the scaffold.
You can get the
This precludes you from storing data in the request scope, though - so
you're left with only storing things in the session scope, which I
wouldn't consider ideal.
Right?
Richard Hightower wrote:
Create a superclass that overides the execute method and calls an abstract
execute method that
January 2004 02:25
To: Struts Users Mailing List
Subject: Re: Mandatory use of form rather than request object
This precludes you from storing data in the request scope, though - so
you're left with only storing things in the session scope, which I
wouldn't consider ideal.
Right?
Richard
Message-
From: Andrew Hill [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 13, 2004 10:09 AM
To: Struts Users Mailing List
Subject: RE: Mandatory use of form rather than request object
No. He would provide setters in the form for anything that needs to be
passed along in request scope. This has
best check that your company doesnt have an OHS
policy against it first ;- )
-Original Message-
From: Patrick Cheng [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 13 January 2004 10:34
To: Struts Users Mailing List; [EMAIL PROTECTED]
Subject: RE: Mandatory use of form rather than request object
12 matches
Mail list logo
