tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Zeigler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-737) Parameter "translate" of TextField is specified as required, but it's realy not required
Date Thu, 04 Jun 2009 16:49:07 GMT

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

Robert Zeigler commented on TAP5-737:

You're confusing the issue of binding vs. specifying. 
The translate parameter absolutely MUST be bound (hence the required flag), or the textfield
won't function.  It's specified as required so that tapestry can catch the lack of binding
early and provide a suitable exception message.

Although the parameter /must/ be bound, it may or may not have to be /explicitly/ bound by
the user: if you don't provide an explicit binding, tapestry will attempt to provide a suitable
binding automatically.  If tapestry is successful, then all is well.  But if it fails, your
page render will fail with an exception explaining that the translate parameter isn't bound.

> Parameter "translate" of TextField is specified as required, but it's realy not required
> ----------------------------------------------------------------------------------------
>                 Key: TAP5-737
>                 URL: https://issues.apache.org/jira/browse/TAP5-737
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions:
>            Reporter: Lukasz Jazgar
>            Priority: Minor
> Components TextField, TextArea and PasswordField have parameter "translate", which is
specified by annotation and in documentation as required.
> This parameter should not be required and it isn't really. 
> Even in examples of using TextField parameter "translate" is not used (http://tapestry.apache.org/tapestry5.1/tapestry-core/ref/org/apache/tapestry5/corelib/components/TextField.html).
> Specification in documentation, specification in annotations,  examples and real behaviour
should be consistent.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message