tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2189) Upload component does not override the isRequired method
Date Wed, 27 Aug 2014 16:51:57 GMT

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

ASF subversion and git services commented on TAP5-2189:
-------------------------------------------------------

Commit 9a3705bc81306bf5d4da33e0b12940fde9c55865 in tapestry-5's branch refs/heads/master from
[~hlship]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=9a3705b ]

TAP5-2189: Upload component does not override the isRequired method


> Upload component does not override the isRequired method
> --------------------------------------------------------
>
>                 Key: TAP5-2189
>                 URL: https://issues.apache.org/jira/browse/TAP5-2189
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-upload
>    Affects Versions: 5.3.7
>            Reporter: Emmanuel DEMEY
>            Priority: Minor
>             Fix For: 5.4
>
>
> There is a bug when an upload field is required. The client-side validation works well,
but I have some bad effect on the server side. 
> The Upload component extends the AbstractField class, that implements the isRequired
method (and returning always false).  So if my field is required, when I create a ValidationDecorator,
the field.isRequired return always false !
> For other inputs, everything is OK, because they are extending the AbstractTextField
class that override again the isRequired method (but with the expected behavior)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message