[jira] [Updated] (TAP5-1694) Ability to override the default NullFieldStrategy

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-1694:
---------------------------------
    Labels: bulk-close-candidate  (was: )

This issue affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent version of Tapestry (currently 5.4.0, available from Maven Central), please update it as soon as possible and add '5.4.0') to the issue's affected versions.

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