[
https://issues.apache.org/jira/browse/TAP5-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-619.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.3
> Add parameter to PropertyEditor to allow custom BeanBlockSource to be used in
> place of the default one
> ------------------------------------------------------------------------------------------------------
>
> Key: TAP5-619
> URL: https://issues.apache.org/jira/browse/TAP5-619
> Project: Tapestry 5
> Issue Type: Wish
> Components: tapestry-core
> Affects Versions: 5.1.0.1
> Reporter: Alfie Kirkpatrick
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.1.0.3
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
