This may or may not be exactly the same thing as in Bug 28358, but it was peculiar. In this case, we were able to simply move a few things around, but it was disconcerting to think that we might be bitten by issues like this in migrating 100% pure java.
Joe
At 9:05 AM -0700 1/25/05, Wendy Smoak wrote:
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-- BeanUtils being unable to set a property when both setProp(int, String) and setProp( String[]). (Actually the bug is about the 'get' side of the problem, but I'm betting it's the same issue.)
http://issues.apache.org/bugzilla/show_bug.cgi?id=28358
I added the beginnings of a test case to demonstrate the problem with setting an indexed property when the bean has both setProp(String[]) and setProp(int, String) methods. It fails with the same 'argument type mismatch' that Will Stranathan was getting.
-- Wendy Smoak
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]