Yes, the User bean contains property named account. But inside the bean it
does not provide setter method because it is purposed to setup when the bean
is created e.g. new User(id, account).
The User bean looks as below:
@Entity
@Table(name="USERS")
public class User implements Serializable{
@Id
private String id;
@Column(name="ACCOUNT")
private String account;
...
public User(String id, String account, String name, String password){
this.id = id;
this.account = account;
this.name = name;
this.password = password;
}
public String getAccount(){
return this.account;
}
/*
public void setAccount(String account){
this.account = account;
}
*/
...
}
cordenier christophe wrote:
>
> But i see in your code
>
> <t:textField t:id="account" t:model="user" t:value="user.account"
> t:validate="required,regexp"/>
>
> Does the User bean has an account property ?
>
>
--
View this message in context:
http://www.nabble.com/Bean-editor-model-for-User-already-contains-a-property-model-for-property-%27account%27-tp25531292p25668232.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
