You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Felix Scheffer (JIRA)" <ji...@apache.org> on 2014/08/15 00:17:18 UTC
[jira] [Updated] (TAP5-736) TextField validate parameter allows
Null, but throws NPE
[ https://issues.apache.org/jira/browse/TAP5-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Scheffer updated TAP5-736:
--------------------------------
Attachment: 0004-TAP5-736-TextField-validate-parameter-allows-Null-bu.patch
The issue still exists in 5.4-beta-17.
Attached patch which adds "allowNull = false" to the "validate" parameter as suggested by Christian Köberl.
> TextField validate parameter allows Null, but throws NPE
> --------------------------------------------------------
>
> Key: TAP5-736
> URL: https://issues.apache.org/jira/browse/TAP5-736
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Labels: bulk-close-candidate
> Attachments: 0004-TAP5-736-TextField-validate-parameter-allows-Null-bu.patch
>
>
> Component TextField has parameter "validate" annotated by
> @Parameter(defaultPrefix = BindingConstants.VALIDATE)
> There is no attribute allowNull, but it has default value "true" (http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/tapestry5/annotations/Parameter.html#allowNull()).
> So null value is allowed according to specification.
> But if you set parameter validate to null, NullPointerException is thrown from AbstractTextProperties.begin(MarkupWriter writer), line: 173.
--
This message was sent by Atlassian JIRA
(v6.2#6252)