[ 
https://issues.apache.org/jira/browse/TAP5-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695374#action_12695374
 ] 

Alfie Kirkpatrick commented on TAP5-619:
----------------------------------------

Thanks. Am already aware of overrides. In this case I do not know the specific 
field names. I want to map property types to custom edit blocks. And I am 
already past beaneditform and beaneditor. I want to create a component around 
propertyeditor directly...

I perhaps could do something cludgy with overrides (will check) but already 
have customisations around beanblocksource, hence the request.

I can probably hack around this by appending my property types with some custom 
string like **SEARCHMODE** and then checking for this in my 
beanblockoverridesource, but setting a specific beanblocksource on 
propertyeditor would be much more elegant ;-)

Perhaps I should have raised this on the mailing list first. If I have followed 
the wrong protocol please let me know, but I saw this as a relatively simple 
and clear cut wishlist request. Regards.

> Provide way to override PropertyEditor.beanBlockSource
> ------------------------------------------------------
>
>                 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
>            Priority: Minor
>
> 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.

Reply via email to