tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1694) Ability to override the default NullFieldStrategy
Date Mon, 22 Aug 2016 06:48:23 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Kemnade closed TAP5-1694.
--------------------------------
    Resolution: Incomplete

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.4.1 or newer), feel free
to provide the necessary information and reopen.

> 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
>              Labels: bulk-close-candidate
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message