tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Quince Wilson (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TAP5-534) Beaneditform validation problem
Date Tue, 24 Feb 2009 15:28:02 GMT

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

Quince Wilson updated TAP5-534:


I just followed the tutorial1.  I attached the project as a tar ball otherwise these snippets
are directly from the tutorial pages specifically Form - part 1 page.  I just cut and pasted
from the site.

 public String getFirstName()
    return firstName;

<t:beaneditform submitlabel="message:submit-label" object="address"/>

> Beaneditform validation problem
> -------------------------------
>                 Key: TAP5-534
>                 URL: https://issues.apache.org/jira/browse/TAP5-534
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.18
>            Reporter: Quince Wilson
>         Attachments: tutorial1.tar.gz
> When following the tutorial with this version all mostly works up to the point where
@Validate("required") is added to Address fields.  A few extra google searches supplied the
missing information.  This annotation seems to have no effect.  I have been able to change
the phone field to an int type and then client validations are generated for that field only,
and you see the bubbles as described by the tutorial.  Otherwise adding @Validate has no effect
on the rendered page.  Viewing the source of the rendered page shows no generated client validations
except when changing the phone type.  By adding an onSuccess method and adding a breakpoint
in eclipse (3.3 with the jetty run plugin) I can inspect the form object and client validations
are false.  Adding clientValidation="true" to the t:beaneditform tag has no effect either.
 This is being ran in eclipse 3.3 with jetty 6.1.15-rc3 run plugin.

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

View raw message