[TAP5-619] Add parameter to PropertyEditor to allow custom BeanBlockSource to be used in place of the default one

• Type: Wish
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.1.0.1
• Fix Version/s: 5.1.0.3
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Alfie Kirkpatrick
• Created: 03/Apr/09 08:41
• Updated: 03/Apr/09 16:52
• Resolved: 03/Apr/09 16:52

Description

I am building a search form and would like to override the default edit blocks with search-style ones. This is conjunction with a HashMap<String, Object> backed bean model. As an example, for dates I want to have a date range block which sends back a start/end range for a date, possibly as a DateRangeSearchTerm against the property name in the hashmap. The search implementation will then know how to convert this into a query to the backend.

I might be pushing the whole BeanEditModel/Conduit framework further than intended? However, doing it this way provides some nice ways to override an auto-built form, eg. by restricting/reordering the properties or by overriding specific blocks even further.