struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: OptionsCollection
Date Fri, 13 Dec 2002 10:49:36 GMT
Also i dont understand why u need to access the request directly.I mean why are 
u setting all the collections as request attributes.GEnerally I think the good 
design is when u r FormBEan represents the screen data.So in this case whatever 
u need on screen will become attribute of form.
I know it does not make much difference in implemantation but as a design it 
becomes pretty straight forward.I mean for an action , if u just look at the 
form, u know what is being displayed.So u just populate the form in action.

Any comments... :-))

-----Original Message-----
From: VEDRE []
Sent: Friday, December 13, 2002 11:44 AM
To: struts-user
Subject: RE: OptionsCollection

You can either use attribute collection="users" for options tag if you store
in request
or you can use               name="formName" property="myList"   if you have
a getMyList() method for the form(You have to fill call formName.setMyList()
in your action class before forwarding to a jsp).

if you have not looked at the documentation.


-----Original Message-----
From: Mark []
Sent: Friday, December 13, 2002 5:36 AM
To: Struts Users Mailing List
Subject: OptionsCollection


I've a number of collections already defined that end up being passed to my
jsp's via the request object.

Users in this case is a map defined in my business logic class that does db
users = (ListUsers).getUsers();


I itertate through this collection using iterate. But now i want to use this
in a select menu. 

Should I be thinking about making my collection available to my FormBean i.e
making a getMyList() method.

Thanks in advance


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message