Because it depends on how dynamic the list is. I only have a few things
which are so unchanging from user to user and screen to screen that they
can go in application scope.
But I use the same mechanism for the objects in request scope that are
lists which depend on an ID or something and so
I have not personally used scaffolding, but by
separating your business logic from your display logic
you gain advantages.
Scaffolding's business beans automatically populate to
certain scopes. You can have many of them per
action-mapping.
By going to a different mapping, but having the
request
Sorry if this is a stupid question, but any help is much appreciated!
I have some drop down lists that I populate in my action class, which means I call
myPage.do each time. This was working nicely, until I tried adding some validation. If
this fails the action class is not called and then when
Need help here too.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 4:52 PM
To: [EMAIL PROTECTED]
Subject: Where to build dropdown lists?
Sorry if this is a stupid question, but any help is much appreciated!
I have some drop down lists
-- nagi
---Original Message---
From: Struts Users Mailing
List
Date: Tuesday, July 15,
2003 02:22:41 PM
To: [EMAIL PROTECTED]
Subject: Where to build
dropdown lists?
Sorry if this is a stupid question, but any
PROTECTED]
subject: Re: Where to build dropdown lists?
hi,
u can set the collection object as the request attribute for the first time
in the action class.
so as long u use the same request , u will not need to repopulate the list
again.
reset is not the right place to populate ur dropdowns
My solution, which is perhaps not the most efficient memory-wise, is to simply put it
in (and retrieve it from) the session rather than the request. Then when I do go
through the populating action, if this is a list that is liable to change often I
reload it from the database. If it is a fairly
I designed a system where I can specify in my action which dropdown
lists I require with a method call. I route my failed validate requests
thro' the action (using the action mapping input tag) every time so the
call is always made, and if I specified it should be in the request, the
system
On Tue, Jul 15,'03 (01:56 PM GMT-0100), Dichotomy wrote:
My solution, which is perhaps not the most efficient memory-wise, is
to simply put it in (and retrieve it from) the session rather than the
request.
I agree this is the best solution (using Session or Application scope).
I brought
On Tue, Jul 15,'03 (02:32 PM GMT+0200), Adam wrote:
I designed a system where I can specify in my action which dropdown
lists I require with a method call. I route my failed validate
requests thro' the action (using the action mapping input tag) every
time so the call is always made, and if
Rick Reumann [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
On Tue, Jul 15,'03 (01:56 PM GMT-0100), Dichotomy wrote:
My solution, which is perhaps not the most efficient memory-wise, is
to simply put it in (and retrieve it from) the session rather than the
request.
I agree
for that had two elements? Is this the way it should work?
Thanks again
IV
from:Dennis [EMAIL PROTECTED]
date:Tue, 15 Jul 2003 13:42:34
to: [EMAIL PROTECTED]
subject: Re: Where to build dropdown lists?
Rick Reumann [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED
On 07/15/2003 08:47:14 AM Rick Reumann wrote:
On Tue, Jul 15,'03 (02:32 PM GMT+0200), Adam wrote:
I designed a system where I can specify in my action which dropdown
lists I require with a method call. I route my failed validate
requests thro' the action (using the action mapping input
On Tuesday 15 July 2003 12:52, [EMAIL PROTECTED] wrote:
Hi,
Another thing that I noticed when playing with the JavaScript pop ups was
that all the validator JavaScript, whether used or not is included in the
JSP code. I ende up with hundreds of lines of JavaScript, including date,
email and
Client-side validation is a useful gimmick at best. I certainly would not trust it in
any web application which will have more than one user (me). It is far too easy to get
around (eg disable javascript?).
--
If education is too expensive, try ignorance.
On Tue, 15 Jul 2003 14:42:34 +0200
Susan Bradeen wrote:
I also use a method call to retrieve my dropdown lists, but I gave up
using an action as the input mapping parameter. I didn't see how I could
implement it without putting a returning from validation check in there
somewhere, and those particular setup actions have become
On 07/15/2003 10:04:13 AM Adam Hardy wrote:
Susan Bradeen wrote:
I also use a method call to retrieve my dropdown lists, but I gave up
using an action as the input mapping parameter. I didn't see how I
could
implement it without putting a returning from validation check in
there
[EMAIL PROTECTED] wrote:
When using the client side validation, there is always a javascript pop up box that says something along the lines of 'Your a thick b*stard, fill in xxx!' Our client requirement is that we produce a list of errors at the top of the page, (the red UL kinda thing), which
On Tue, Jul 15,'03 (04:04 PM GMT+0200), Adam wrote:
Since it's in my action base class, I never have to worry about
programming it manually.
If you are always going to check that the List is there in your
BaseAction class, why not just give the List application scope on start
up and not
19 matches
Mail list logo
