[WICKET-668] PropertyResolver.getPropertySetter() depends on calling PropertyResolver.setValue() first for it to work.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0-beta3
• Assignee: Unassigned
• Reporter: Alastair Maw
• Created: 18/Jun/07 19:01
• Updated: 24/Jul/07 20:56
• Resolved: 24/Jul/07 20:56

Description

See PropertyResolverTest#testGetTargetSetter() for details.

We go like this:

Method method = PropertyResolver.getPropertySetter("number", address);
assertEquals(method.getName(), "setNumber");

However, the method variable will be null unless someone has previously called setValue() on that field.

This is asking for hard-to-reproduce NPEs.

I discovered this while refactoring PropertyResolver to make it clean up properly when the application goes away. The tests are now cleaning up properly on setUp()/tearDown(), so this came to light.