[BEANUTILS-144] PropertyUtils.setProperty Ignores Property Setter

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5

Environment

Operating System: Windows XP
Platform: Other

• Bugzilla Id: 14440
• Assignee: Unassigned
• Reporter: Runako Godfrey
• Created: 11/Nov/02 18:57
• Updated: 25/Mar/08 08:08
• Resolved: 25/Mar/08 08:08

Description

When using PropertyUtils to set a property on an object that implements the
Map interface, undesirable behavior can result. In my case, I was trying to
use PropertyUtils (via BeanUtils) to set a property on an object of type
org.apache.util.Criteria, which implements Map. Using
PropertyUtils.setProperty ignores properties for which there is a legitimate
setter, instead placing the value in the map. It would be more intuitive if
the value were placed in the map only if no setter existed.

Here is sample code that illustrates this problem:

public class PropertyUtilsTest extends TestCase {
private static final String TEST_VAL = "_test-val_";

public void testPropUtils() {
try

{ Criteria c = new Criteria(); PropertyUtils.setSimpleProperty(c, "dbName", TEST_VAL); assertEquals(TEST_VAL, c.getDbName()); }

catch (Throwable t)

{ t.printStackTrace(); }

}
}

In this case, Criteria implements a setDbName() method that will not be called
by this code. This is somewhat confusing.