tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sundsskard (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1694) Ability to override the default NullFieldStrategy
Date Thu, 13 Oct 2011 13:52:11 GMT

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

David Sundsskard commented on TAP5-1694:
----------------------------------------

The symbol feature in TAP5-1677 might be an option?
                
> Ability to override the default NullFieldStrategy
> -------------------------------------------------
>
>                 Key: TAP5-1694
>                 URL: https://issues.apache.org/jira/browse/TAP5-1694
>             Project: Tapestry 5
>          Issue Type: Wish
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: David Sundsskard
>
> My use-case is that I want empty textfields to post an empty String instead of null.

> I have implemented a nullfieldstrategy and it can be set on the textfield, but components
that create textfields on the fly (eg. Grid) use the default NullFieldStrategy defined in
AbstractTextField.
> I can't contribute a new "defaults" as that conflicts. 
> It would be nice to be able to override the strategy defined in AbstractTextField.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message