After rereading your original post (and the spec), I'm inclined to agree
that what you're trying should work.
But this does not appear to work for me (JRun 2.3.3, Build 152, JDK
1.2).
Sounds like a bug. Have you checked the reference implementation?
Thanks for the comments.
I have now tried
andowska
Software Engineer
http://www.AgDomain.Com
-Original Message-
From: Richard Dallaway [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Monday, June 28, 1999 3:07 AM
Subject: Re: Q: set bean param from -OPTION- list
My example would have been better if I had the sy
In JSP 1.0/1.1, neither setProperty nor getProperty have any provision
for indexed properties.
Hans Bergsten wrote:
I don't agree. In the JSP 1.0 spec, indexed properties are mentioned
explicitly for setProperty. The description could be clearer, but I know the
intention was to support
public void setFoo(int index, String value)
or even something like:
public void setFoo(String[] values)
..and expect jsp:setProperty to "do the right thing" and supply me with
getParameterValues("foo").
In JSP 1.0/1.1, neither setProperty nor getProperty have any provision for
indexed
PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]; [EMAIL PROTECTED]
[EMAIL PROTECTED]; [EMAIL PROTECTED]
[EMAIL PROTECTED]
Date: Monday, June 28, 1999 11:28 AM
Subject: Re: Re: Q: set bean param from -OPTION- list
From: "Lance Lavandowska" [EMAIL PROTECTED]
To get their individual values
My example would have been better if I had the syntax right.
Let me try again.
With a HTML SELECT list (or set of checkboxes), what is the easiest way to
collect the OPTION values with a jsp:useBean?
For example:
FORM ACTION="/test.jsp" METHOD="POST"
SELECT MULTIPLE NAME="foo"
OPTION
With a HTML SELECT list, what is the easiest way to collect the OPTION
values with a jsp:useBean?
For example:
SELECT NAME="foo"
OPTION VALUE="1" First option
OPTION VALUE="2" Second
OPTION VALUE="3" Last
/SELECT
...I select all three options and submit to a JSP which has the
following:
