RE: html:options and html:select

If your list stores objects which is the type of Struts' LabelValueBean (provides only getValue() and getLabel() methods), then you can simply as Jiin-Her Lu (816) 926-2145 >>> [EMAIL PROTECTED] 02/02/04 06:31AM >>> Hi Frank Try using Request.setAttribute("collectionName",list);

RE: html:options and html:select

lto:[EMAIL PROTECTED] Gesendet: Montag, 2. Februar 2004 13:22 An: Struts Users Mailing List Betreff: Re: html:options and html:select you can do the following: "> 'property' of the select box should be the name of the property in your FormBean that you wish to

RE: html:options and html:select

Hi Frank Try using Request.setAttribute("collectionName",list); I have tried putting the Collection as the request attribute never in the form bean. One more thing make user you provide exact path of CProduct in the name field. Regards Anant -Original Message- From: Otto,

Re: html:options and html:select

ArrayList productList = new ArrayList(); CProduct product = new CProduct(); product.setId(new Integer(1)); product.setName("My Product"); productList.add(product); request.setAttribute("products",productList.toArray()); ... -- If you dont want to have a refering action then you can have an

Re: html:options and html:select

you can do the following: "> 'property' of the select box should be the name of the property in your FormBean that you wish to store the selected value in. You then iterate through the list in your form by using the tag. For every object in your list an tag is written, wher

Re: html:options maximum length?

I think you should re-think your UI design. Besides being very slow, the select box will be very annoying and difficult for the end user to use. You should try and narrow down the users choices before they get to the select box page so that you only need to show a few dozen options at most. Reg

Re: html:options

ECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Subject: Re: html:options Date: Sun, 12 Oct 2003 09:51:17 -0500 name/value pairs from a database are handled nicely in a list of LabelValueBeans. I'd pull the code to load that list from the database out into a model clas

Re: html:options

name/value pairs from a database are handled nicely in a list of LabelValueBeans. I'd pull the code to load that list from the database out into a model class, or perhaps into a Singleton loaded by an InitServlet (at startup - if the contents weren't changing, or were at least application-wide) The

RE: html:options list source question

: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Sunday, July 13, 2003 9:22 PM To: 'Struts Users Mailing List' Subject: RE: html:options list source question Craig Berry wrote: > The jsp page contains an html:form section linked via action mapping > to the EditDeForm type. > In it

RE: html:options list source question

Craig Berry wrote: > The jsp page contains an html:form section linked via action mapping to the EditDeForm type. > In it, there is a select/options section that looks like this: > > > property="value" > labelProperty="label"/> > > I had thought that this would be enough to make it wor

RE: html:options

-Original Message- From: sjones [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 09, 2003 10:43 AM To: [EMAIL PROTECTED] Subject: html:options Good Morning Everyon

Re: html:options can not automatically match value

U can use tag instead of . This will retain the selected value . From: "lcl" <[EMAIL PROTECTED]> Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: html:options can not automatically match value Date: Thu, 5 Jun 2003 10:57

Re: html:options can not automatically match value

Maybe you need to specify the name of the form bean before the property="projclieid" e.g. and maybe the collection name should not be the com.nsk.gs.sales.ClientInfo but the name you put in the request from the action class before you call the jsp The estateOfficesNames is an attr

Re: html:options can not automatically match value

Sakis, Thank you very much. I have done as you mentioned, but the result has not changed. I have tried to changed the collection name to com_nsk_gs_sales_ClientInfo(of course, do it in action form to set a same named attribute in session), and add a name attribute in html:selection tag , which wil

RE: html:options

hey thanksmaybe I'll try to minimize my code. -Original Message- From: Abhinav (Cognizant) [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 12:15 PM To: Struts Users Mailing List Subject: RE: html:options I was able to do it like

RE: html:options

I was able to do it like that. Thanks a lot all you ppl. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 9:39 PM To: [EMAIL PROTECTED] Subject: RE: html:options There are other optiosn to use

RE: html:options

27, 2003 5:44 PM To: Struts Users Mailing List Subject: RE: html:options correct me if I am wrong. This would work if getOptionList() returns an array of String. In my case array is of Objects and one attribute of that object has to be displayed. -Original Message- From: [EMAIL PROTECTE

RE: Html:Options usage

thanks for replying but the solution doesn't work, so I changed it a bit: and I got this error: Error Message: No getter method available for property filter0 for bean under name org.apache.struts.taglib.html.BEAN Error Code: 500 Target Servlet: null Error Stack: javax.servlet.js

RE: Html:Options usage

-Original Message- From: e gg [mailto:[EMAIL PROTECTED] Sent: 17 March, 2003 15:16 To: [EMAIL PROTECTED] Subject: Html:Options usage Hi, I have a bean class that returns an ArrayList of ArrayLists for my dropdowns. I am really confused on how to show this dropdowns. Here's my

Re: Html:options

if you use with or , the option that equals the formbean property value will be automaticaly selected. (formbean initialized with name="foo") foo bar nop will render Nico. > Is there a way of obtaining a element where one of the > sub-elements has the SELECTED attribute ? >

Re: RE: html:options selected attribute

ist <[EMAIL PROTECTED]> Subject: RE: html:options selected attribute > > Take your pick of http://marc.theaimsgroup.com/?l=struts-user&m=103416927522003&w=2 http://marc.theaimsgroup.com/?l=struts-user&m=103313043614360&w=2 http://marc.theaimsgroup.com/?l

RE: html:options selected attribute

truts Users Mailing List Subject: Re: html:options selected attribute I am not exactly following the logic here. Could you elaborate a little more? Thanks, Jason ---Original Message--- From: Slobodan Kasterovic <[EMAIL PROTECTED]> Sent: 02/12/03 08:24 AM To: 'Struts Users Ma

Re: html:options question

Thanks it work!. -Gus D. Rick Reumann wrote: On Monday, January 6, 2003, 2:14:38 PM, Gus wrote: GD> GD> labelProperty="label"/> GD> GD> Example. the options are "Read-only", "Admin", and "Analyst" that's the GD> order of the collection, when I edit a user that is Admin, I want the

Re: html:options question

On Monday, January 6, 2003, 2:14:38 PM, Gus wrote: GD> GD> labelProperty="label"/> GD> GD> Example. the options are "Read-only", "Admin", and "Analyst" that's the GD> order of the collection, when I edit a user that is Admin, I want the GD> drop-down to show with the "Admin" being s

Re: html:options question

I did something similar, with optionsCollection (which I like). Here is my code: for optionsCollection, my "property" is the name of my bean, and I think you have to pluralize it (example availablecourselabel --> availablecourselabels) to indicate that it's a collection. The "label" and "

RE: html:options encoded property

Correct me if I'm wrong, but aren't the "e; entries unnecessary? Couldn't you just remove them? -Original Message- From: Nathalie Foures [mailto:[EMAIL PROTECTED]] Sent: Monday, December 09, 2002 9:52 AM To: [EMAIL PROTECTED] Subject: html:options encoded property Hi! I wrote a JSP page

Re: html:options ordering

Dennis Muhlestein wrote: I have a hashtable with key/value that get displayed by an html:options tag. Works ok, but they are ordered in reverse order of the id. That isn't any performance problem, but it looks a little strange to the user. For instance, what if you wanted the options in alphab

Re: html:options ordering

Thanks for the comments. Seems to make more sense not to have any ordering functionality in the html:options tag anyway. On Wed, 2002-10-30 at 10:40, Dennis Muhlestein wrote: > I have a hashtable with key/value that get displayed by an html:options > tag. > > Works ok, but they are ordered in

RE: html:options ordering

> -Original Message- > From: Dennis Muhlestein [mailto:dennis@;zserve.com] > Sent: Wednesday, October 30, 2002 9:41 AM > > I have a hashtable with key/value that get displayed by an > html:options > tag. > > Works ok, but they are ordered in reverse order of the id. That isn't > any p

Re: html:options ordering

Hash Tables don't guarantee order when you pull them out enmasse. probably best bet is to store it in a list and sort accordingly (Collections.sort). Dennis Muhlestein wrote: I have a hashtable with key/value that get displayed by an html:options tag. Works ok, but they are ordered in rever

RE: html:options

The first technique couples your presentation with your business logic more closely than does the latter. So, my preference would be using the . You can maintain the collection that makes up the options in the form bean for the page. Initialization must be handled via the associated action cl

RE: Html:options question help

Try adding type="com.whatever.Engineer" > > labelProperty="name" property="id"/> > HTH James Mitchell Software Engineer\Struts Evangelist Struts-Atlanta, the "Open Minded Developer Network" http://struts-atlanta.open-tools.org > -Original Message- > From: Eyassu, Daniel [m

RE: html:options must be enclosed within html:select

gt; To: "Struts Users Mailing List" <[EMAIL PROTECTED]> cc:(bcc: David Hay/Lex/Lexmark) Subject: RE: html:options must be enclosed within html:select Have you looked at the source for OptionTag yet? The first thing it does is check for a SelectTag in the pageContext. I beli

RE: html:options must be enclosed within html:select

Have you looked at the source for OptionTag yet? The first thing it does is check for a SelectTag in the pageContext. I believe it is forcing this because it needs to know if it should render it as "selected". If you need the functionality of Options, but need to write your own select, I would s

RE: html:options with a Map collection

I should know..I'm still cleaning my wounds! ;) JM > -Original Message- > From: Chappell, Simon P [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, May 14, 2002 12:04 PM > To: Struts Users Mailing List > Subject: RE: html:options with a Map collection > > >

RE: html:options with a Map collection

' End, Inc. (608) 935-4526 >-Original Message- >From: Galbreath, Mark [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, May 14, 2002 10:50 AM >To: 'Struts Users Mailing List' >Subject: RE: html:options with a Map collection > >

RE: html:options with a Map collection

That's great! But a Map is still not a Collection. -Original Message- From: Sriram Nookala [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 14, 2002 11:32 AM To: Struts Users Mailing List Subject: Re: html:options with a Map collection I got this to work using the following:

Re: html:options with a Map collection

I got this to work using the following: where "getReportTemplates" returns the Map. - Original Message - From: "Galbreath, Mark" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Sent: Tuesday, May 14

RE: html:options with a Map collection

A Map is not a Collection. Mark -Original Message- From: Sriram Nookala [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 14, 2002 10:48 AM To: Struts Users Mailing List Subject: Re: html:options with a Map collection I've been trying to find documentation on how to use a Map colle

Re: html:options with a Map collection

I've been trying to find documentation on how to use a Map collection in html:options with the Map key as the label name and the Map value as the label property. thanks, sriram -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: html:options

Thanks, it looks so trivial now. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 3:02 PM To: Struts Users Mailing List Subject: RE: html:options JM > -Original Message- > From: Jay

RE: html:options

--Select Report Type-- Thanks, Dean Chen -Original Message- From: Leonardo Maciel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 2:55 PM To: 'Struts Users Mailing List' Subject: RE: html:options insert line like this: Actually sho

RE: html:options

insert line like this: Actually should do -Original Message- From: Jayaraman Dorai [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 2:52 PM To: [EMAIL PROTECTED] Subject: html:options Hi, I want in my drop down a blank record. This needs to be the

RE: html:options

JM > -Original Message- > From: Jayaraman Dorai [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 01, 2002 2:52 PM > To: [EMAIL PROTECTED] > Subject: html:options > > > Hi, > > I want in my drop down a blank record. This needs to be the > default.

Re: html:options Iterator Creation error -

If PersonalForm has a Collection getSecurityOptions(); method then it does look OK. This shouldn't matter, but you could try a type property with bean:define -Ted. Sunder wrote: > > Hi, > I am trying to implement the html:options tag in one of our > applications, > > I have a form bean w

Re: html:options problem with labelProperty

quick wild guess.. one of the calls to getMerchandiseCategoryDescriptions() returns null. try returning "it was null" if you are about to return a null. --- Allen Walker <[EMAIL PROTECTED]> wrote: > I have the following: > > [html:select property="merchandiseCategory"] > [html:options propert

Re: html:options bug?

The collection attribute needs the bean reference only. The dot notation is for your property. Because the collection isn't the bean itself you'll have to use a define tag or something to make a bean reference directly to your collection, then use that reference in your collection attribute.

Re: html:options and FormBean

> "Francois" == Francois Duchaussoy <[EMAIL PROTECTED]> writes: Francois> Hi, Francois> I have an ActionForm with a Collection object inside. Francois> I'd like to use the tag to display that Collection. Francois> Could anyone give me an example on how to do that? Franco

Re: html:options with FormBean

There are two ways but the best way is to set up a simple bean like "LabelValueBean" that has two attribute; the option value and the option description public class LabelValueBean { String label, descrip ; public String getLabel() { ... } public void setLabel( String newValu

Re: html:options & collection of beans in FormBean

The ActionForm itself is a bean "in some scope". The name is whatever you specified in struts-config. People tend to send the options collection over seperately from the form (your #1), since it usually a seperate query and sometimes used in more than one place. But referring to the ActionForm it

Re: HTML:OPTIONS

be the simplest thing. Thank you, Chris Princeton Lau wrote: > Chris, > > What sort of errors are you getting? > > Below is a reprint of a message I posted a few weeks ago. I believe it > addresses a similar question. > > Princeton > > Re: html:options

RE: HTML:OPTIONS

Chris, What sort of errors are you getting? Below is a reprint of a message I posted a few weeks ago. I believe it addresses a similar question. Princeton Re: html:options not understanding collections from form beans

Re: html:options not understanding collections from form beans?

Hello, I struggled with the options tag because I did not understand what it meant by 'collection'. I could not pass a collection along with a request because I was at my index page. In other words, nothing had been done yet. I instantiated the bean that had the collection and then used a t

Re: html:options from a Collection of Strings

In subscription.jsp (webapp struts example), you can see : ... <% java.util.ArrayList list = new java.util.ArrayList(); list.add(new org.apache.struts.webapp.example.LabelValueBean("IMAP Protocol", "imap")); list.add(new org.apache.struts.webapp.example.LabelValueBean("POP3 Protocol", "pop3"

RE: html:options value and label

Hi, TGIF from me too :) I guess you could try using an iterate tag because it seems that the values you want are just a sequence, which you can expose using the indexId attribute. Otherwise you will need to specify both the property and labelProperty attributes of the options tag, which lets you

Re: html:options not understanding collections from form beans ?

On Tue, 10 Jul 2001, Ted Husted wrote: > Can you post some of the code you are working with? > > Given a method getDirectoryName() you should be able to pass the same > collection to both the labelName and labelProperty properties. > > Though, you may need to expose the collection as a bean (in p

Re: html:options not understanding collections from form beans ?

Can you post some of the code you are working with? Given a method getDirectoryName() you should be able to pass the same collection to both the labelName and labelProperty properties. Though, you may need to expose the collection as a bean (in page scope). The tags are not written with the ass