Yeah, I wonder about that bug: we've recently been moving some
application servers from Solaris to Linux, and I think this is a JVM
level issue. Just before we started, someone had posted about this
to the Struts users' list (although I can't seem to find it in the
archives right now.) Basica
From: "Joe Germuska" <[EMAIL PROTECTED]>
> I haven't actually looked at this in a running debugger, or with log
> output, but the code which governs this ultimately is
> PropertyUtilsbean.setIndexedProperty(...)
I found what I think is an open bug about the original issue that was
raised-- BeanUt
At 7:58 AM -0700 1/25/05, Larry Meadors wrote:
There are two things about BU that irritate me (and that is the level
- irritation, not a show stopper by any stretch of the imagination).
1) If I have an Integer (or any Number subclass) property, and someone
keys in "joe", BU turns it into 0 by defau
There are two things about BU that irritate me (and that is the level
- irritation, not a show stopper by any stretch of the imagination).
1) If I have an Integer (or any Number subclass) property, and someone
keys in "joe", BU turns it into 0 by default. That is the last thing I
want it to do. Ze
At 9:14 PM -0700 1/24/05, Larry Meadors wrote:
Nope, actually, it is bean-utils that is at fault here (something all
struts developers should be accustomed to saying - IMO, bean-utils is
the single weakest component in struts).
According to the javabeans specification
(http://java.sun.com/products/
And to be perfectly honest, I didn't know for sure - I just threw it
together using Netbeans, and ASSUMED since I was array-backing it, I'd
use an indexed property.
However, I know better now - that if I intend to pass the same property
name multiple times NOT to use indexed accessor/mutators,
From: "Larry Meadors" <[EMAIL PROTECTED]>
Nope, actually, it is bean-utils that is at fault here (something all
struts developers should be accustomed to saying - IMO, bean-utils is
the single weakest component in struts).
I stand corrected, it even _says_ (8.3.3) that 'an indexed property might be
Nope, actually, it is bean-utils that is at fault here (something all
struts developers should be accustomed to saying - IMO, bean-utils is
the single weakest component in struts).
According to the javabeans specification
(http://java.sun.com/products/javabeans/docs/spec.html), indexed
properties
From: "Will Stranathan" <[EMAIL PROTECTED]>
> Well, I understand the way HTTP is working there, it just SEEMS to be
> that having the additional method (setBar(int, String)) confused
> BeanUtils or something - because removing those methods (making no
> other changes) cleared the problem up.
Your
Well, I understand the way HTTP is working there, it just SEEMS to be
that having the additional method (setBar(int, String)) confused
BeanUtils or something - because removing those methods (making no
other changes) cleared the problem up.
w
On Mon, 24 Jan 2005 17:15:01 -0500
Jeff Beal <[EMAI
It's related to a difference in how the HTTP request parameters are
built. With the "indexed properties" that you had, the BeanUtils
classes are going to look for parameters whose names include the index.
That is 'bar[1]', 'bar[2]', etc.
HTML:select with multiple=true sends multiple parameter
>
> Pretty simple. There may be a better way to do it, but this works just fine
> for me.
And your not usinng the generics package like Will is.
>
> --Brad
>
> -Original Message-
> From: Will Stranathan [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 24, 2005
THANKS! After all that work, I *think* BeanUtils was having issues
with setNumber(int, String) for some reason - when I took out the
setters for indexed values, and just have setters/getters for the
arrays - it works like a champ!
Thanks a TON!
Will Stranathan
On Mon, 24 Jan 2005 15:16:55 -060
eCd();
for(int i=0; imailto:[EMAIL PROTECTED]
Sent: Monday, January 24, 2005 3:11 PM
To: user@struts.apache.org
Subject: Select Multiple Issues
I had posted earlier concerning this, and haven't gotten any response,
but I think it got lost in all the spirited discussions about
constants i
I had posted earlier concerning this, and haven't gotten any response,
but I think it got lost in all the spirited discussions about
constants interfaces, leadership voting, etc. over the past week.
I've done a lot of searching, and AFAICT, I'm trying all the right
things, but it's still not wo
Does anybody have a good example of an ActionForm/ combo that works? I've been banging my head against
a wall for a week now trying to figure out what the issue is. With
tracing turned on, the Struts RequestProcessor IS receiving a
String[], but when BeanUtils attempts to call the setters in m
16 matches
Mail list logo
