Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Message-ID: <1082285654.1238761573042.JavaMail.jira@brutus>
Date: Fri, 3 Apr 2009 05:26:13 -0700 (PDT)
From: "Alfie Kirkpatrick (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Subject: [jira] Commented: (TAP5-619) Provide way to override
 PropertyEditor.beanBlockSource
In-Reply-To: <1932854974.1238748192894.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Hi Thiago, I take your points but just for the record, while BeanBlockSource can be overridden, currently the same service is injected in all cases. I want to specify a particular BeanBlockSource instance for a particular PropertyEditor in my page. PropertyEditor is not classed as 'internal' so I don't see a problem in principle with this as a wishlist item...

> 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.