[
https://issues.apache.org/jira/browse/TAP5-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-735.
-------------------------------------
Assignee: Howard M. Lewis Ship
Resolution: Invalid
Just because your definition of "not null" doesn't match Tapestry's or the
documentations, doesn't mean it's a bug. Sorry.
> All parameters "NOT Allow Null"
> -------------------------------
>
> Key: TAP5-735
> URL: https://issues.apache.org/jira/browse/TAP5-735
> Project: Tapestry 5
> Issue Type: Bug
> Components: documentation
> Affects Versions: 5.1.0.5
> Reporter: Lukasz Jazgar
> Assignee: Howard M. Lewis Ship
>
> In documentation, all component's parameters have flag "NOT Allow Null"
> regardless of attribute allowNull of @Parameter annotation.
> For example:
> Component TextField (sources: AbstractTextField.java) 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.
> In documentation
> (http://tapestry.apache.org/tapestry5.1/tapestry-core/ref/org/apache/tapestry5/corelib/components/TextField.html)
> parameter "validate" has flag: "NOT Allow Null".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
