[TAPESTRY-111] component parameters with direction 'form' should not allow static bindings

• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Affects Version/s: 3.0
• Component/s: Framework
• Environment: Operating System: All; Platform: All
• Bugzilla Id: 26416
• Assignee: Howard Lewis Ship
• Reporter: glongman
• Created: 26/Jan/04 00:00
• Updated: 27/Aug/04 05:59
• Resolved: 27/Aug/04 05:59

Description

Currently Tapestry plods along oblivious when a user uses a static to bind to a
component parameter with direction 'form'.

By definition a form parameter property is read and used to update the binding
when the component is rewound. Elsewhere in the framework an exception is
thrown if an attempt to update a static binding. This is currently does not
happen in the case of 'form'. The rewind appears to occur without incident but
no update occured.

This is an problem that can easily be experienced by users who are using
implicit components and forget to prepend thier parameter expression
with "ognl:". Its tricky to track this down unless you are aware that the
parameter in question has direction 'form'.

Tapestry (it has been suggested the ParameterManager) should catch the fact the
someone is using a static to bind to a parameter with direction 'form' and
throw an exception.