[TAP5-1549] ParameterWorker forces evaluation of default method, even if the parameter is bound by other means

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.5
• Fix Version/s: 5.3
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Robert Zeigler
• Created: 16/Jun/11 05:55
• Updated: 07/Jul/11 21:51
• Resolved: 07/Jul/11 19:43

Description

The revised implementation of ParameterWorker evaluates the defaultXXX method regardless of whether or not the parameter is bound. This can easily lead to application exceptions, particularly when the defaultXXX value is computed rather than static.

For example, loop's "encoder" parameter attempts to get a ValueEncoder from ValueEncoderSource. This will fail if, for instance, the loop's value is a hibernate entity with a multi-column PK, even if the developer binds a custom ValueEncoder to the parameter to handle the entity. Admittedly, this case has a workaround: contribute the custom encoder to ValueEncoderSource. But that's only one edge case.

The correct solution is to lazily evaluate defaultXXX methods.